Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore: Automatically remove status: labels when issue is closed #8964

Open
HonkingGoose opened this issue Mar 3, 2021 · 1 comment
Open

chore: Automatically remove status: labels when issue is closed #8964

HonkingGoose opened this issue Mar 3, 2021 · 1 comment
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:refactor Refactoring or improving of existing code

Comments

@HonkingGoose
Copy link
Collaborator

What would you like Renovate to be able to do?

@viceice suggested that we remove any status: labels from issues that are closed.

Did you already have any implementation ideas?

If we agree that this is a good thing to do, we should automate stripping status: labels from closed issues, because we will forget to do this 95% of the time, including me... 😄 🙃
@HonkingGoose HonkingGoose added priority-5-triage status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality) priority-4-low Low priority, unlikely to be done unless it becomes important to more people and removed priority-5-triage labels Mar 3, 2021
@HonkingGoose HonkingGoose mentioned this issue Mar 3, 2021
Closed
@rarkins
Copy link
Collaborator

rarkins commented Mar 3, 2021

Yes, let's have an action that runs on issue close and:

  • Fetches the list of labels
  • Checks for any starting with status:
  • Removes any it has found

IIRC the default GITHUB_TOKEN has rights to change labels.

For ones that are already closed we can remove them manually quite easily.

@rarkins rarkins added status:ready and removed status:requirements Full requirements are not yet known, so implementation should not be started labels Mar 3, 2021
@rarkins rarkins added type:refactor Refactoring or improving of existing code and removed type:feature Feature (new functionality) labels Jan 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people type:refactor Refactoring or improving of existing code
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rarkins @HonkingGoose