This repository has been archived by the owner on Jun 2, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: add initial set of org-wide labels
- Loading branch information
1 parent
b51ca13
commit f96ddbd
Showing
1 changed file
with
104 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,22 +1,118 @@ | ||
# Repository labels to be synced across the entire org. | ||
# For picking hex colors, you can use: https://www.htmlcolor-picker.com/ | ||
# Every item must have a name, color, and description. | ||
|
||
- name: ":hammer and wrench: maintenance" | ||
color: "169509" # grassy green | ||
description: "Work that must be done for platform health" | ||
# Notes: | ||
# * Repositories may define their own labels as long as they don't | ||
# conflict with what's listed here. If it turns out a repository-specific | ||
# label would be useful to have in the entire organization, we can always add | ||
# it here post facto. | ||
# * We have added these based on need. They are not all-encompassing. If something | ||
# seems missing, feel free to open a PR. | ||
# * Whenever a repo has a matching label, that label will be updated. If there | ||
# is no matching label, the label will be created anew. "Matching" is determined | ||
# by comparing the label's lowercased name, with all puncutation, emoji, and special | ||
# chars removed. | ||
# * For picking hex colors, you might use: https://www.htmlcolor-picker.com/ | ||
# Describe your color with a comment so it's easier to review. | ||
|
||
|
||
### LABELS INDICATING HOW ISSUES CAN BE ENAGAGED WITH. | ||
|
||
- name: "good first issue" | ||
color: "42dd35" # friendly lime green | ||
description: "A good task for a newcomer to start with" | ||
|
||
- name: "help wanted" | ||
color: "54976d" # fenway green | ||
description: "Ready to be picked up by anyone in the community" | ||
|
||
|
||
### LABELS INDICATING BROAD THEMES OF WORK. | ||
### MORE THAN ONE OF THESE MAY APPLY AT A TIME. | ||
|
||
- name: "maintenance" | ||
color: "ff9125" # construction orange | ||
description: "Relates to platform health and/or routine upkeep" | ||
|
||
- name: "security" | ||
color: "f0d165" # caution yellow | ||
description: "Relates to improving to the security posture of the platform" | ||
|
||
- name: "enhancement" | ||
color: "a2eeef" # electric blue! | ||
description: "Relates to new features or improvements to existing features" | ||
|
||
- name: "documentation" | ||
color: "0052cc" # royal blue | ||
description: "Relates to documentation improvements" | ||
|
||
|
||
### LABELS INDICATING THE SCOPE OR FUNCTION OF THE ISSUE. | ||
### AT MOST ONE OF THESE SHOULD BE USED AT A TIME. | ||
|
||
- name: "depr" | ||
color: "3c3cc3" # indigo-blue | ||
description: "Proposal for deprecation & removal per OEP-21" | ||
|
||
- name: "bug" | ||
color: "d93f0b" # scarlet red... | ||
description: "Report of or fix for something that isn't working as intended" | ||
|
||
- name: "discovery" | ||
color: "d876e3" # a curious shade of lavendar | ||
description: "Pre-work to determine if an idea is feasible" | ||
|
||
- name: "epic" | ||
color: "7e027e" # epic violet | ||
description: "Large unit of work, consisting of multiple tasks" | ||
|
||
- name: "initiative" | ||
color: "340963" # formidably deep mauve | ||
description: "Huge unit of work, consisting of multiple epics" | ||
|
||
|
||
### LABELS INDICATING ISSUE OUTCOMES. | ||
|
||
- name: "wontfix" | ||
color: "ffffff" # white | ||
description: "This will not be worked on" | ||
|
||
- name: "duplicate" | ||
color: "cfd3d7" # duplicitous grey | ||
description: "This issue or pull request already exists elsewhere" | ||
|
||
|
||
### LABELS USED IN THE OPEN EDX CONTRIBUTION WORKFLOW. | ||
### PLEASE CONSULT WITH OPEN EDX PROJECT MANAGMENT BEFORE CHANGING THESE. | ||
|
||
- name: "waiting on author" | ||
color: "bfd6f6" # baby blue | ||
description: "PR reviewers are waiting on the author to answer questions, fix tests, etc." | ||
|
||
- name: "closed-inactivity" | ||
- name: "inactive" | ||
color: "cc950a" # clay-ish brown | ||
description: "PR author has been unresponsive for several months" | ||
|
||
- name: "closed inactivity" | ||
color: "dbcd00" # gold | ||
description: "PR was closed because the author abandoned it" | ||
|
||
- name: "needs test run" | ||
color: "f5424b" # crimson red | ||
description: "Author's first PR to a repository, awaiting test authorization from Axim" | ||
|
||
- name: "good first issue :tada:" | ||
color: "42dd35" # lime green | ||
description: "A good task for a newcomer to start with" | ||
- name: "open source contribution" | ||
color: "f0f0f0" # light grey | ||
description: "PR author is not from Axim or 2U" | ||
|
||
- name: "blocked by other work" | ||
color: "ffa500" # yellow orange | ||
description: "PR cannot be finished until other work is complete" | ||
|
||
- name: "product review" | ||
color: "c97bf7" # light puple | ||
description: "PR requires product review before merging" | ||
|
||
- name: "core contributor" | ||
color: "000000" # black | ||
description: "PR is Core Contributor with rights in this repository (manually added)" |