You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when you're creating bulk PRs to several hundred repositories, see release-drafter app -> action transition and now the reusable workflow one, repository maintainers often lack labels release-drafter honors (or ignores) for CD actions and changelog creation.
Therefore I'd like to ask if it's possible to:
add the release-drafter labels as organization default on the jenkinsci org to apply them automatically on newly created repositories
add the labels retroactively to already existing repositories, if the labels don't exist yet. I'm not sure how feasible and desired that is, but according to the GH API docs, a couple of calls take care of it.
Resources: Listing all repositories, creating new labels
The named proposals can't mitigate the issue of repository maintainers not using labels, but making the lifecycle for repository maintainers easier by removing the need to create more than a couple of dozen labels, if you repository lacks them, and passively promoting the use of release drafter to generate changelogs.
Service(s)
GitHub
Summary
Currently, when you're creating bulk PRs to several hundred repositories, see release-drafter app -> action transition and now the reusable workflow one, repository maintainers often lack labels release-drafter honors (or ignores) for CD actions and changelog creation.
Therefore I'd like to ask if it's possible to:
Resources: Listing all repositories, creating new labels
The labels in question are available at: https://github.com/jenkinsci/.github/blob/master/.github/release-drafter.yml#L10-L66.
The named proposals can't mitigate the issue of repository maintainers not using labels, but making the lifecycle for repository maintainers easier by removing the need to create more than a couple of dozen labels, if you repository lacks them, and passively promoting the use of release drafter to generate changelogs.
This issue continues the discussion from jenkinsci/file-parameters-plugin#107.
Reproduction steps
No response
The text was updated successfully, but these errors were encountered: