-
Notifications
You must be signed in to change notification settings - Fork 38.8k
ci: avoid running git diff after patching #29461
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
Conversation
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. Code CoverageFor detailed information about the code coverage, see the test coverage report. ReviewsSee the guideline for information on the review process.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update. |
|
It is there to clarify the CI is using different code than the one in the source dir. lgtm ACK c835176 |
Oh that makes sense. If you think it would be an improvement, I could change the patch command to |
|
Sure, anything is fine here. |
Drop `git diff` command so it is easier to run CI locally if git checkout is a worktree. Currently it fails because the directory is not recognized as a git repository. The `git diff` command was added recently in bitcoin#28359 commit fa07ac4 and can be avoided just by teeing the patch to stdout
|
Updated c835176 -> 84388c9 ( |
|
lgtm ACK 84388c9 I can't review this, since it is written in bash, but given that CI passed and something is printed in the log, I guess this is fine 🤷♂️ |
|
Added milestone, since this is a bugfix |
sedited
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK 84388c9
Drop
git diffcommand so it is easier to run CI locally if git checkout is a worktree. Currently it fails because the directory is not recognized as a git repository.The
git diffcommand was added recently in #28359 commit fa07ac4 and can be avoided just by teeing the patch to stdout