feat: use commit hash as release target #171
Merged
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
|
No linked issues found. Please add the corresponding issues in the pull request description. |
guilhermelimak
force-pushed
the
feat/add-release-target
branch
from
22a9131
to
5d5db7e
Compare
This will avoid commits made on master after the release PR was created to be included in the release.
guilhermelimak
force-pushed
the
feat/add-release-target
branch
from
71e1ece
to
b93ddf2
Compare
|
@simoneb This is ready for review |
simoneb
approved these changes
Nov 13, 2022
guilhermelimak
changed the title
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.
Set the release branch name as target to avoid merging the changes commited to the main branch after the release PR is created to be included in the release.
References #167