Labels
Labels
37 labels
- Aaargh!
- Concerns dependencies of the project
- Concerns developers' experience with the codebase
- Improvements or additions to documentation
- Concern a release of the project
- Pull requests that update a dependency file
- No cause and effect relationships can be determined. Need to stabilize quickly
- Cause and effect can only be deduced in retrospect, and there are no right answers
- The relationship between cause and effect requires analysis or expertise
- It's to late to perform any action. Cause and effect are no longer sense here
- Represents the "known knowns" issue. It's Obviously
- Pull requests that update GitHub Actions code
- Pull requests that update Go code
- Good for newcomers
- Extra attention is needed
- Priority 1 - Must be fixed ASAP
- Priority 2 - Stalls work on the project or its dependents
- Priority 4 - Low priority and doesn't need to be rushed
- Priority 3 - Not blocking but should be fixed soon
- This is created be a sponsor of project
- This was closed because it has been inactive for 12 days since being marked as stale
- This prevent slote process on this object
- This is stale because it has been open for 30 days with no activity.
- This is unstale due on an activity
- This is done!
- This issue or pull request already exists
- We needs more information to go forwards
- After investigation, we decide to stop because we can't reproduce with current informations
- This is confirmed, will work on soon
- Has not been triaged & therefore, not ready for work