Checkout actions fetches whole repository #953
Merged
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
Previously the repository did not checkout a single branch but actually a single commit, which it made into a unique ref for its own repo. Consequently, when attempting to rebase the entire history of gh-pages onto that commit the rebase would fail, because the base in the repo wasn't the actual master branch but only its latest commit which resulted in an unfitting history of that commit and a failing rebase. Now that we check out everything from the start, this should work fine. Signed-off-by: l-1sqared <[email protected]>
|
Force merged. Change is comparatively simple and has been tested. Also I want it this to work for the next release, which is due |
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.
Previously the repository did not checkout a single branch but actually a single commit, which it made into a unique ref for its own repo. Consequently, when attempting to rebase the entire history of gh-pages onto that commit the rebase would fail, because the base in the repo wasn't the actual master branch but only its latest commit which resulted in an unfitting history of that commit and a failing rebase.
Now that we check out everything from the start, this should work fine.
Signed-off-by: l-1sqared [email protected]