Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
renovate
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
GitHub Mirror
Renovate Bot
renovate
Commits
489bd2c3
Commit
489bd2c3
authored
4 years ago
by
Rhys Arkins
Browse files
Options
Downloads
Patches
Plain Diff
docs: status labels
parent
08a187a8
No related branches found
Branches containing commit
Tags
38.47.0
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/development/issue-labeling.md
+16
-0
16 additions, 0 deletions
docs/development/issue-labeling.md
with
16 additions
and
0 deletions
docs/development/issue-labeling.md
+
16
−
0
View file @
489bd2c3
...
@@ -16,6 +16,22 @@ Most issues should have a label relating to either a platform, manager, datasour
...
@@ -16,6 +16,22 @@ Most issues should have a label relating to either a platform, manager, datasour
## Label categories
## Label categories
### Status
<details>
<summary>
Status of issue
</summary>
status:requirements
status:blocked
status:ready
status:in-progress
</details>
Use these to label the status of an issue.
For example, use
`status:requirements`
to mean that an issue is not yet ready for development to begin.
All open issues should have some
`status:*`
label applied.
### Type of issue
### Type of issue
<details>
<details>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment