-
-
Notifications
You must be signed in to change notification settings - Fork 861
Maintenance on label_directory.json #7940
Copy link
Copy link
Closed
Labels
Complexity: SmallTake this type of issues after the successful merge of your second good first issueTake this type of issues after the successful merge of your second good first issueFeature: Refactor GHARefactoring GitHub actions to fit latest architectural normsRefactoring GitHub actions to fit latest architectural normsLang: GHAGitHub ActionsGitHub Actionsmilestone: missingrole: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 0.5ptCan be done in 3 hours or lessCan be done in 3 hours or less
Metadata
Metadata
Assignees
Labels
Complexity: SmallTake this type of issues after the successful merge of your second good first issueTake this type of issues after the successful merge of your second good first issueFeature: Refactor GHARefactoring GitHub actions to fit latest architectural normsRefactoring GitHub actions to fit latest architectural normsLang: GHAGitHub ActionsGitHub Actionsmilestone: missingrole: back end/devOpsTasks for back-end developersTasks for back-end developerssize: 0.5ptCan be done in 3 hours or lessCan be done in 3 hours or less
Type
Projects
Status
Done
Overview
We want to keep
label_directory.jsonand the labels themselves up to date by performing periodic housekeeping.Action Items
2 weeks inactivelabel was deleted, then added back by a developer: Consolidate the id for the new2 weeks inactivewith the 'labelKey' and 'labelName' values of the corresponding, previous label. (Including 'Description' and 'Color')NEW-from 'labelKey' for all intentional new labelsResources/Instructions