-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Diff might be inaccurate if HEAD's parent is an ancestor of BASE #11
Comments
@joshgubler would love your review on #13 if/when you have a second. |
🎉 This issue has been resolved in version 0.3.0-next.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
@joshgubler, I've implemented the changes we discussed. Could you please test this latest version (above) and provide feedback on its functionality? If everything works as expected, I'll create a full release. Thank you for your help with testing! |
I got the following error:
I was able to merge the branch without a merge conflict, so that isn't the problem. Is there a bug in the |
Here's a simple reproduction of the issue in a public repo: |
Any chance you could try v0.3.0-next.2 please 🙏 |
|
This should hopefully fix it now https://github.com/swade1987/github-action-kustomize-diff/releases/tag/v0.3.0-next.3 |
Looks like git want's you to set the committer identity before it can create the merge commit. This can be anything since you're not going to push the commit anywhere. Sorry if this is turning into more work than it is worth. |
I'm happy to keep testing for you. Or feel free to fork my test repo if you don't want to wait for me. |
Don't worry we will get there as I think it's a valid feature. I'll take a look next week and keep you posted. Thanks in advance and the continued testing. |
If a change is made to the BASE branch in parallel to the HEAD branch, the diff from this module indicates that the change will be reverted. Git, however, is smart enough to know that the change should not be reverted when the PR is merged.
It's very easy to get into this state if the person creating the PR doesn't
git pull
before creating their feature branch.Rather than comparing the output from kustomize on BASE with the output on HEAD, it would be better to compare the output on BASE with the output after merging HEAD to BASE. Obviously, this merge should only happen locally on the runner and not be pushed.
The text was updated successfully, but these errors were encountered: