feat: Pull and rebase before push #231
Merged
Conversation
This file contains hidden or 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
Resolves #229 If another user pushes changes to the remote repo after gitopscli has cloned it, the subsequent push will fail. Alliviate this problem by pulling and rebasing local changes on top of any remote changes just before pushing.: For the case of creating a new branch (for a PR), the pull is skipped because it would fail due to the missing remote branch.
joachimprinzbach
approved these changes
Jul 10, 2024
|
🎉 This issue has been resolved in version 5.9.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
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.
Resolves #229
If another user pushes changes to the remote repo after gitopscli has cloned it, the subsequent push will fail. Alliviate this problem somewhat by pulling and rebasing local changes on top of any remote changes just before pushing.
For the case of creating a new branch (for a PR), the pull is skipped because it would fail due to the missing remote branch.