Skip to content

Issues: bisq-network/style

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

13 Open 1 Closed
13 Open 1 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Do not reorganize imports, field variables, or anything else
#15 opened Nov 15, 2019 by freimair
Do not use else if and else clauses where return statements make them redundant
#12 opened Jun 6, 2018 by cbeams
Do not declare local variables as final
#11 opened Jun 6, 2018 by cbeams
2
Use shared Editorconfig settings
#10 opened May 2, 2018 by cbeams
Follow the seven rules laid out in "How to Write a Git Commit Message"
#9 opened May 1, 2018 by cbeams
Place Bisq AGPL license header at top of all Java sources
#8 opened Mar 20, 2018 by cbeams
3
Submit pull request reviews using GitHub's "Review changes" button
#7 opened Mar 20, 2018 by cbeams
Use Bitcoin Core-style ACK / NACK / Nit language in pull request reviews
#6 opened Mar 20, 2018 by cbeams
Wrap comments at 90 characters
#5 opened Mar 16, 2018 by cbeams
Check the "Allow edits from maintainers" box in pull requests
#4 opened Mar 16, 2018 by cbeams
Wrap code at 120 characters
#3 opened Mar 16, 2018 by cbeams
3
Organize imports with common layout
#2 opened Mar 14, 2018 by cbeams
Capture style tips and conventions as GitHub issues
#1 opened Jan 31, 2018 by cbeams
ProTip! Type g i on any issue or pull request to go back to the issue listing page.