Skip to content

Avoid implicitly fetching when adding a new git remote - #6990

Merged
samcoe merged 2 commits into
trunkfrom
remote-add-no-fetch
Feb 7, 2023
Merged

samcoe merged 2 commits into
trunkfrom
remote-add-no-fetch

Conversation

@mislav

@mislav mislav commented Feb 7, 2023

Copy link
Copy Markdown
Contributor

Auto-fetching is not always necessary and it can fail when adding a git remote for a just-created fork since the git objects might not yet be available on the platform.

Fixes #6975

Auto-fetching is not always necessary and it can fail when adding a git remote for a just-created fork since the git objects might not yet be available on the platform.
@mislav
mislav requested a review from a team as a code owner February 7, 2023 20:20
@mislav
mislav requested review from vilmibm and removed request for a team February 7, 2023 20:20
@samcoe
samcoe enabled auto-merge (squash) February 7, 2023 21:07
@samcoe
samcoe merged commit 14eb873 into trunk Feb 7, 2023
@samcoe
samcoe deleted the remote-add-no-fetch branch February 7, 2023 21:22
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

Successfully merging this pull request may close these issues.

failed to add remote gh repo fork --remote

4 participants