ci: add rebase on end of release process #361
Open
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
| run: | | ||
| git fetch --no-tags origin 2-dev:2-dev | ||
| git rebase ${GITHUB_REF_NAME} 2-dev | ||
| git push origin 2-dev |
There was a problem hiding this comment.
Will not work since it require a force push (commit IDs are refresh each time you rebase). Note that the CI user will become the author/co-author of each rebased commit
There was a problem hiding this comment.
Here that just, add the commit chore(release): x.x.x-beta.y [skip ci] created by semantic-release to the dev branch, as what is done in other repositories
There was a problem hiding this comment.
there's no force push as it is fast forward in principle
etrousset
requested changes
Aug 30, 2024
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.
What does this PR do ?
Simply add rebase on end of release process to keep linear history