Feature: `blockingLabels`

[koppor]

Type of feature

💡 Feature

Current behavior

Currently, all issues can be taken. The idea of take-action is to have "blocking labels".

Note: This feature is more a nice to have. I posted it for completeness...

The take-action is recommended at https://github.com/community/maintainers/discussions/447#discussioncomment-10756193 - thus read by many people. I added a recommendation to this action below 😅, because I like the unassign feature.

Suggested solution

• blocking_labels: A list of labels that will prevent the action from running if they are present on the issue.
• blocking_labels_comment: The message to display to the user if the issue has a blocking label.

(Inspired by https://github.com/bdougie/take-action?tab=readme-ov-file#usage)

Additional context

No response

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

Contributing Docs

• [X] I agree to follow this project's Contribution Docs

[takanome-dev]

Well, we do have required_label and that means the action will not run if the issue does not contain that label.

It's kinda the same as having blocking labels...

What we can add is a comment to let know the contributors that the issue is not up for grab yet.

What do you think @koppor ?

[koppor]

There are three kinds of issues:

1. intended to be taken by /assign-me
2. not intended to be taken by /assign-me
3. undefiend :) to be taken by /assign-me

With "required" labels, one defines group 3 to be group 2. With "blocking" labels, one defines group 3 to be group 1 instead.

For my use case, the current solution works. If someone else needs the feature, they can rise a comment here.