jenkins-infra / jenkins-infra/github-reusable-workflows
Test Release Drafter usage on backport branches
Open
- Dominant language
- No language data
- Stars
- 1
- Forks
- 10
- Avg merge
- 2h 34m
- Merged PRs (30d)
- 1
Description
Currently the action assumes that there is a `next` pseudo-version for Release Drafter. This system likely does not make much sense when backport branches are involved. Should the action detect that it is running on a nondefault branch and just skip the usage of Release Drafter?
Contributor guide
Assessment
This issue has not been assessed yet.