-
Notifications
You must be signed in to change notification settings - Fork 648
Repository: Extract run_command()
function
#4365
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
@bors r+ |
📌 Commit 4c63e20 has been approved by |
🔒 Merge conflict This pull request and the master branch diverged in a way that cannot be automatically merged. Please rebase on top of the latest master branch, and let the reviewer approve again. How do I rebase?Assuming
You may also read Git Rebasing to Resolve Conflicts by Drew Blessing for a short tutorial. Please avoid the "Resolve conflicts" button on GitHub. It uses Sometimes step 4 will complete without asking for resolution. This is usually due to difference between how Error message
|
☔ The latest upstream changes (presumably #4364) made this pull request unmergeable. Please resolve the merge conflicts. |
4c63e20
to
eb2f671
Compare
@bors r=locks |
📌 Commit eb2f671 has been approved by |
☀️ Test successful - checks-actions |
This new function makes it easier to run arbitrary
git
commands in the working folder of the local index clone. It was extracted from thesquash_index()
background worker tasks, which uses it to rungit push --force-with-lease
, which is not yet supported by thegit2
crate.The main goal of this PR is to reduce the visibility of the
checkout_path
andcredentials
fields on theRepository
, which outside code should ideally not have any access to.Note that this includes the commits from and is based on #4363.