-
Notifications
You must be signed in to change notification settings - Fork 202
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
fix issues with applying PR patch in --from-pr #3414
Merged
boegel
merged 15 commits into
easybuilders:develop
from
Flamefire:fix_git_patch_permissions
Aug 18, 2020
Merged
fix issues with applying PR patch in --from-pr #3414
boegel
merged 15 commits into
easybuilders:develop
from
Flamefire:fix_git_patch_permissions
Aug 18, 2020
Conversation
This file contains 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
boegel
requested changes
Aug 18, 2020
boegel
reviewed
Aug 18, 2020
0d55a77
to
176028d
Compare
1955deb
to
75c1f62
Compare
boegel
requested changes
Aug 18, 2020
Co-authored-by: Kenneth Hoste <[email protected]>
Changing into the directory of the patch is not required and might even lead to unexpected results as calling code will suddenly run in a different PWD if the patch happens to be compressed
boegel
requested changes
Aug 18, 2020
boegel
requested changes
Aug 18, 2020
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.
We need to get this covered by the tests too, done in Flamefire#3
enhance test for apply_patch to also cover applying patches with git
Flamefire
commented
Aug 18, 2020
boegel
approved these changes
Aug 18, 2020
1 task
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.
When PRs introduce only new files determining the patch level fails which makes it skip the whole
git am
part even though the level is not even required. Hence as a first part of the fix the level determination is skipped when using git to apply the patch.Secondly
git am
requires an active git repo but we download the base branch via the archive, not a clone. Also the parameterpatch
is likely wrong as I can't find it in the docu. Hence replace that withgit apply
which does work for regular folders too.Fixes #3411