LABELS.md: add workflow: labels
Signed-off-by: Patrik Oldsberg <poldsberg@gmail.com>
This commit is contained in:
@@ -82,11 +82,17 @@ These labels indicate that an issue is related to specific domains of expertise.
|
||||
- `domain:tooling` - Tooling and automation in Node.js and GitHub Actions.
|
||||
- `domain:web` - Frontend development using TypeScript and React.
|
||||
|
||||
## Workflow Labels
|
||||
|
||||
These labels indicate a workflow status for the owners.
|
||||
|
||||
- `workflow:do-not-merge` - The Pull Request should not be merged.
|
||||
- `workflow:before-release` - Should be handled before the next main-line release.
|
||||
- `workflow:after-release` - Should be handled after the next main-line release.
|
||||
- `workflow:after-vacations` - To be handled once the owners return from vacation.
|
||||
|
||||
## General Labels
|
||||
|
||||
- `after vacations` - To be handled once the owners return from vacation.
|
||||
- `do not merge` - The pull request should not be merged.
|
||||
- `fix before release` - Should be handled before the next release.
|
||||
- `good first issue` - Good for new contributors.
|
||||
- `stale` - The issue or pull request has not seen any activity for a while and will be closed if no further activity is seen.
|
||||
- `no stale` - The issue or pull request should not be closed due to inactivity.
|
||||
|
||||
Reference in New Issue
Block a user