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.

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

status/triage label via GH Action, type: via GitHub template #10192

Closed
HonkingGoose opened this issue May 27, 2021 · 3 comments
Closed

status/triage label via GH Action, type: via GitHub template #10192

HonkingGoose opened this issue May 27, 2021 · 3 comments
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality)

Comments

@HonkingGoose
Copy link
Collaborator

We could maybe use an Action to apply triage/status labels to new Issues and only apply type: labels automatically by GitHub, that way you only have to change one label and not 3 when you are creating issues? Could help for all types of issues, not just refactor

Originally posted by @rarkins in #10037 (comment)

@HonkingGoose HonkingGoose added priority-4-low Low priority, unlikely to be done unless it becomes important to more people status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality) labels May 27, 2021
@HonkingGoose
Copy link
Collaborator Author

I've rescued this comment from the previous issue, as that issue is about to get closed. 😉

@HonkingGoose
Copy link
Collaborator Author

I found a action that we could use to add/remove labels: andymckay/labeler. It's made by a GitHub Staff member.

It looks like it would do most of what we want: adding/removing labels on issues and/or pull_request events.
There's a open issue that requests support to remove all labels.

The README of the action is easy to understand, and the project seems to be stable enough for production use.
The repository has Dependabot enabled for security updates (there's a Dependabot security PR for lodash that's not merged yet).

Link to action repository: https://github.com/andymckay/labeler

I'll wait for your review on the safety/suitability of this action before proceeding.

@rarkins
Copy link
Collaborator

rarkins commented May 27, 2021

It doesn't seem to support the sophistication we need. Eg we want to "assign triage priority if none set" and "assign requirements status if none set"

@rarkins rarkins closed this as not planned Won't fix, can't repro, duplicate, stale May 14, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 14, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority-4-low Low priority, unlikely to be done unless it becomes important to more people status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality)
Projects
None yet
Development

No branches or pull requests

2 participants