🌱 Fix git in Prow #2769
Merged
🌱 Fix git in Prow #2769
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
Newer versions of git have a security measure in place to prevent git from parsing the .git/config file or running any hooks if the user running git is not the owner of the repository files. Prow runs as a random UID, which is not guaranteed to be the same as the UID that owns the cloned files, so this change disables the ownership check and considers all cloned repositories "safe" regardless of owner. Signed-off-by: Andy Goldstein <andy.goldstein@redhat.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Looks like this fixed the issue. Self-merging to unblock other PRs. |
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.
Summary
Newer versions of git have a security measure in place to prevent git from parsing the .git/config file or running any hooks if the user running git is not the owner of the repository files. Prow runs as a random UID, which is not guaranteed to be the same as the UID that owns the cloned files, so this change disables the ownership check and considers all cloned repositories "safe" regardless of owner.
Related issue(s)
Fixes #