Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / bisq-network/style issues and pull requests

#15 - Do not reorganize imports, field variables, or anything else

Issue - State: open - Opened by freimair almost 5 years ago

#14 - The commit history of all repos should be kept clear

Issue - State: closed - Opened by erciccione about 5 years ago - 3 comments

#14 - The commit history of all repos should be kept clear

Issue - State: closed - Opened by erciccione about 5 years ago - 3 comments

#13 - Add 'when not to use curly braces' entry to style README

Pull Request - State: closed - Opened by ghubstan about 5 years ago - 2 comments

#11 - Do not declare local variables as final

Issue - State: open - Opened by cbeams over 6 years ago - 2 comments

#11 - Do not declare local variables as final

Issue - State: open - Opened by cbeams over 6 years ago - 2 comments

#10 - Use shared Editorconfig settings

Issue - State: open - Opened by cbeams over 6 years ago

#8 - Place Bisq AGPL license header at top of all Java sources

Issue - State: open - Opened by cbeams over 6 years ago - 3 comments

#5 - Wrap comments at 90 characters

Issue - State: open - Opened by cbeams over 6 years ago

#4 - Check the "Allow edits from maintainers" box in pull requests

Issue - State: open - Opened by cbeams over 6 years ago

#3 - Wrap code at 120 characters

Issue - State: open - Opened by cbeams over 6 years ago - 3 comments

#2 - Organize imports with common layout

Issue - State: open - Opened by cbeams over 6 years ago

#1 - Capture style tips and conventions as GitHub issues

Issue - State: open - Opened by cbeams almost 7 years ago