Issue Rejection Workflow#93
Merged
marwin89 merged 1 commit intoUltraStar-Deluxe:mainfrom Jul 29, 2025
Merged
Conversation
Applying and removing the "Rejected" based on issue status saves manual work and ensures consistency across issues.
codello
force-pushed
the
issue-management
branch
from
f2ca209 to
3fa5bb5
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR adds a GitHub workflow that automatically manages the "Rejected" label on issues. When an issue is closed as "not planned", the label is added. When it is reopened, the label is removed.
Closes Issue(s)
None
Motivation
Managing labels on issues can be error-prone and is often a manual step. This is a step to automate label management where possible.
Additional Notes
The "Rejected" label basically just duplicates the same information that is provided by the "not planend" status. It might also make sense to remove the label entirely. Issues can be filtered via
is:issue is:closed reason:not-plannedanyway (which would be my preferred approach).