FAQ_Labels
The managers of the twofactorauth repo (aka the contributors) like to use different labels to make it easier to filter through the list of issues and PRs.
Here's a list of our custom labels and how we use them:
| Label Name | Description |
|---|---|
 |
Used when a PR is closed (usually due to inactivity), but isn't merged. Encourages someone else to make another PR, adding/updating the sites in the old one. |
 |
Used when an issue has a bug bounty attached for finding a solution. |
 |
Used when an issue or PR highlights a fix to a bug. |
 |
Used when an issue or PR highlights a bug. |
 |
Used when an issue or PR is a duplicate of another issue/PR. |
 |
Used when a PR contains enhancements to the overall design or code of the site. |
 |
Used when the owner of the PR isn't responding to comments, and indicates that the PR might be closed. |
 |
Used when an issue or PR fits our international site support milestone. Gradually being phased-out. |
 |
Used when a contributor has looked over the PR, and it's ready for another contributor to merge. |
 |
Used when a PR isn't up-to-date with the master branch, and it must be updated before merging. |
 |
Used when a PR contains sites to add to the repo. |
 |
Used when an issue or PR contains information worth looking over in the future. |
 |
Used when a PR is pending changes suggested by a contributor. |
 |
Used when an issue contains a request to add or update a site within the repo, and encourages someone else to make a PR. (Often used when the owner of the issue doesn't know how to create a PR.) |
 |
Used when an issue contains a question. |
 |
Used when a PR contains sites already added to the repo that have been updated. |
 |
Used when an issue or PR has been updated after a contributor suggested a change. |
 |
Used when an issue or PR is up for voting. |