fix: #895 Image Updater continuously force-pushes new commits when checkout branch is specified #911
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.
Fixes #895
This PR changes how a custom git write-back branch is created. Please review and look for any side effects. See issue comments #895 (comment)
Tested with the following scenarios with the following app config:
push-branch
does not exist. image-updater creates the new branch from the checkout branchmain
, and writes the update to the filepush-branch-kustomize/source/.argocd-source-argocd_push-branch-kustomize.yaml
push-branch
, and no changes are committed or pushed.push-branch
to commit and push the updates.