ER: Modify "Update Label Directory" workflow to recover from accidental deletion #7883
Closed
2 of 5 tasks
Labels
Complexity: Large
Feature: Refactor GHA
Refactoring GitHub actions to fit latest architectural norms
role: back end/devOps
Tasks for back-end developers
size: 8pt
Can be done in 31-48 hours
Emergent Requirement - Problem
Whenever a label is deleted (accidentally or not) from the repo, the label gets removed from all issues that previously had that label. Creating a new label with the same name does not recover those issues- this information is lost. We need a mechanism to either re-apply labels when they are deleted from the repo, and/or notify us that this has happened.
On Jan 20th, a dev deleted the
2 weeks inactive
label. The label was removed from over 20 issues. When the "Schedule Friday" automation ran 5 days later, it appears that the bot created a replacement label. However, the replacement is unique and does not equate to the original label.Issue you discovered this emergent requirement in
Date discovered
2/3/25
Did you have to do something temporarily
Who was involved
@t-will-gillis
What happens if this is not addressed
In this case, 24 issues were un-labeled without us knowing. This will break / cause an error in the label automations when those are active.
Resources
Recommended Action Items
Potential solutions [draft]
Workflow logs showing initiating action, label deletion, and label removal ('unlabeled')
The text was updated successfully, but these errors were encountered: