Skip to content
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

GitDriver: try to fetch default branch from remote #10687

Merged
merged 2 commits into from Apr 1, 2022

Conversation

glaubinix
Copy link
Contributor

The initial clone determined what the default branch of the cache git repository was. Changing it on the remote didn't have any impact on the local data. However, cloning it on a different machine would then store a different default branch on that machine. This could lead to different results for the same command on different machines.

Unfortunately, I couldn't find a way to update the default branch on the local cache because checkout and symbolic-ref are both unavailable.

The initial clone determined what the default branch of the cache git repository was. Changing it on the remote didn't have any impact on the local data. However, cloning it on a different machine would then store a different default branch on that machine. This could lead to different results for the same command on different machines.
@glaubinix glaubinix force-pushed the f/git-driver-remote-default-branch branch from 89af7e5 to fcf690a Compare April 1, 2022 13:24
Co-authored-by: Jordi Boggiano <j.boggiano@seld.be>
@Seldaek Seldaek merged commit ef12e42 into composer:main Apr 1, 2022
@Seldaek Seldaek added this to the 2.3 milestone Apr 1, 2022
@Seldaek Seldaek added the Bug label Apr 1, 2022
@glaubinix glaubinix deleted the f/git-driver-remote-default-branch branch April 1, 2022 15:56
emahorvat52 pushed a commit to emahorvat52/composer that referenced this pull request Feb 3, 2023
The initial clone determined what the default branch of the cache git repository was. Changing it on the remote didn't have any impact on the local data. However, cloning it on a different machine would then store a different default branch on that machine. This could lead to different results for the same command on different machines.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants