chore: configure Release Drafter to use releases from a single branch only #2819
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vlsi
force-pushed
the
drafter_branch
branch
4 times, most recently
from
77ce948
to
f52f67c
Compare
|
Are there any instructions on how to use this or is it just automatic ? |
|
It does not yet work as expected, however, it is automatic. Here's what it currently does (see v42.5.5): https://github.com/pgjdbc/pgjdbc/releases I've created several releases manually in order to aid it, however, the script can't figure out the latest release yet. It does not understand 42.5.4 was on 42.5.x branch. Currently, it should select 42.5.2 as a baseline for the main branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.