Skip to content
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

Using git resolve-conflict with "both added" conflict shows a fatal error #5

Open
phil-blain opened this issue Feb 11, 2022 · 0 comments

Comments

@phil-blain
Copy link

For "both added" conflicts, git show :1:path/to/file yields a fatal error since there is nothing in stage 1. This does not crash the script since the script does not use set -e, and the file where the output from git show is redirected ends up being empty (which is the right result), but it would be nice to detect that situation and avoid the command in that case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant