This repository was archived by the owner on Mar 30, 2026. It is now read-only.
Repository navigation
Fixed subgit pull issue - #52
Merged
Merged
Conversation
Author
|
Okay so the last push checks is the repo is cloned previously and if it is, checks whether the remote commit sha and the local commit sha matches. If they don't a 'git pull' is executed. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
So in the previous code, after the inital cloning of a repo, subgit would only fetch and create a local branch based on the
revision: branch:in the.subgit.ymlfile. This creates a problem because while fetching from the remote, nothing is merged locally, which in turn created a bug if you had any un-pulled changes as shown in issue: #50The change made is only a change from
fetch()topull()which seems to do the trick while testing.This is the relevant output i got when i tried to replicate the issue invoking
DEBUG=1:git log output before change:
Relevant subgit pull output after the change:
git log after change:
Refers to issue #50