https://github.com/bisq-network/github
The @bisq-network GitHub organization
https://github.com/bisq-network/github
Last synced: 10 months ago
JSON representation
The @bisq-network GitHub organization
- Host: GitHub
- URL: https://github.com/bisq-network/github
- Owner: bisq-network
- Created: 2017-07-23T14:09:18.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2018-01-22T12:39:36.000Z (almost 8 years ago)
- Last Synced: 2025-01-15T16:57:11.460Z (12 months ago)
- Homepage:
- Size: 21.5 KB
- Stars: 4
- Watchers: 5
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# The bisq-network GitHub organization
## Our label prefix scheme for GitHub Issues
Generally speaking, labels across all repositories in the @bisq-network GitHub organization conform to the following prefix scheme:
- `a` / `an`: indicates the _type_ of issue being dealt with, e.g. `a:bug`, `a:feature`, `a:meeting`, `an:idea`
- `in`: indicates what subsystem or module of a codebase the issue is located in, e.g. `in:UI`, `in:network`, `in:arbitration`
- `on`: indicates which specific operating systems an issue applies to, e.g. `on:macOS`, `on:Linux`, `on:Windows`
- `re`: indicates which cross-cutting concerns and external dependencies an issue regards, e.g. `re:privacy`, `re: testing`, `re:Tor`, `re:Bitcoin`
- `was`: indicates why an issue was closed, if it was closed for any other reason than being complete/fixed, e.g. `was:duplicate`, `was:moved`, `was:superseded`