context: opt-in pull request head ref #551
Merged
+41
−9
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
crazy-max
force-pushed
the
git-pr-head-ref-optin
branch
2 times, most recently
from
4aa93b9 to
042dcea
Compare
crazy-max
force-pushed
the
git-pr-head-ref-optin
branch
from
042dcea to
0f25bd7
Compare
|
I assume this matches actions/checkout ? |
Yes indeed |
Signed-off-by: CrazyMax <1951866+crazy-max@users.noreply.github.com>
crazy-max
force-pushed
the
git-pr-head-ref-optin
branch
from
0f25bd7 to
e02b7d7
Compare
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.
related to
Using the
/headref for pull requests by default is problematic, as it fails to capture upstream changes in the target branch. This discrepancy might lead to different outcomes in CI runs compared to those obtained when running the same workflows against the target branch after merging a PR.With this change, users will need to set the
DOCKER_DEFAULT_GIT_CONTEXT_PR_HEAD_REF=trueenvironment variable in their workflows to opt in to tracking theHEADof the development branch, rather than the merge branch that previews the changes after merging into the target branch.cc @chandanpg