Check release label / label_check workflow failure is annoying

[mathbunnyru]

Troubleshooting docs

• My problem is not solved in the Troubleshooting docs

Anaconda default channels

• I do NOT use the Anaconda default channels (pkgs/* etc.)

How did you install Mamba?

Other (please describe)

Search tried in issue tracker

label, label_check

Latest version of Mamba

• My problem is not solved with the latest version

Tried in Conda?

Not applicable

Describe your issue

Every time I create a PR, I get the CI failure, because of the label_check workflow.
And I also get an email and notification from GitHub that my build failed.

I think devs with some permissions don't have this issue, but all new contributors do, and that's not pleasant.
Maybe there is a better way?

mamba info / micromamba info

No response

Logs

No response

environment.yml

No response

~/.condarc

No response

[mathbunnyru]

I think it is also makes it less clear which PRs have green CI in PRs list.

[jjerphan]

Yes, I agree.

The best solution I see is to have authors or issues and PRs be able to label theirs.

[JohanMabille]

The release scripts are based on these labels, so we definitely need this check. Maybe we can provide a PR template that will let the user choose the appropriate label.