chore: check for non-labeled issues

[ph1l1pF]

Changes

This PR will create a new workflow that once in a week will check all open issues and search if any of them are not labeled correctly. If all of them are labeled as expected, it'll cleanly complete the job, otherwise, a new issue reporting the unlabeled issues will be created.

I have tested the action on a test repository: https://github.com/ph1l1pF/renovate-test/issues

Context

Closes #16273

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[rarkins]

Can we determine what the results would be for this repo prior to merging? e.g. via a console output or running the same logic manually locally?

[HonkingGoose]

First round of review.

I'll review the Bash script soon. 😉

[HonkingGoose]

Second round of reviews, this time for the comments in the script.

After the suggestions and changes have been made, we need to check the technical bits of the Bash script itself.

[rarkins]

Could you explain what the Label check action label is used for? And in particular: is this solution impossible without it?

[rarkins]

Could you explain what the Label check action label is used for? And in particular: is this solution impossible without it?

Could the issue be identified instead using author + issue title?

[ph1l1pF]

Could you explain what the Label check action label is used for? And in particular: is this solution impossible without it?

Could the issue be identified instead using author + issue title?

@rarkins The label is just a way to identify the issue that lists the other issues. Title + author (bot) ist also possible. This would have the benefit that no label has to be created. I can try that.

[ph1l1pF]

Could you explain what the Label check action label is used for? And in particular: is this solution impossible without it?

Could the issue be identified instead using author + issue title?

@rarkins The label is just a way to identify the issue that lists the other issues. Title + author (bot) ist also possible. This would have the benefit that no label has to be created. I can try that.

@rarkins I have done it. This has even simplified the script a little:)

[rarkins]

Label check action

Found 12 issues missing type: labels:

• group:fusionjs is invalid #33087
• Meta: Why users cannot create Issues directly #32830
• Support SSH keys as secrets #32083
• Complete the work for the json-jsonata manager #28925
• Support devbox #27543
• Separate out "logs" auto message into more categories #27349
• Support for Unity editor #27295
• Save repo cache even if dry run #27034
• Clean up repo http cache after each run #27032
• Improve config option metadata to define where options can be used and improve JSON schema #26571
• Support detectGlobalManagerConfig for Maven settings.xml #23009
• Separate npm/yarn/pnpm managers #5607

Found 3 issues missing priority: labels:

• group:fusionjs is invalid #33087
• Composer: unsupported value if != constraint used #31504
• Support MSBuild SDK extraction from Import element #29420

[HonkingGoose]

Some small text changes.

[secustor]

Else LGTM, but would prefer to keep all tools in the JS/TS ecosystem for maintenance

[renovate-release]

🎉 This PR is included in version 39.72.1 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 39.72.1

Your semantic-release bot 📦🚀