FIX Set fetch-depth for parent-branch #31
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
40 tasks
emteknetnz
force-pushed
the
pulls/1.1/checkout-depth
branch
from
e6c699b
to
0434f60
Compare
GuySartorelli
approved these changes
Jul 11, 2022
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.
Issue #11
POC here where fetch-depth of 3 is being set on a pr with 2 commits - https://github.com/emteknetnz/silverstripe-crazy-egg/runs/7274566968?check_suite_focus=true - in the git log section the commits 'test2' and 'test commit' are from the pull-request branch. The other commits 'Update test.yml' (2x) are from the base branch and and 'Merge ec2aa658707711be843ab3eed2b4c8423d0514f4 into 7809da2c97c9af56c5eace31fe6dc295f37b1c29' is the proposed merge-commit