revert changes to set associated head sha on pull request event #239
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
Signed-off-by: CrazyMax <crazy-max@users.noreply.github.com>
jedevc
approved these changes
Oct 17, 2022
|
Thank you for understanding the impact and reverting it this soon. Kudos 👍🏻 |
tonistiigi
approved these changes
Oct 17, 2022
torsdag
added a commit
to ftrackhq/ftrack-actions
that referenced
this pull request
Mar 14, 2023
5 tasks
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.
fixes #238
follow-up #234 (comment)
cc @gustavovalverde @ianschmitz
revert changes to set associated head sha on pull request event and use commit sha that triggered the workflow by default. User can still set associated head sha on PR by setting the env var
DOCKER_METADATA_PR_HEAD_SHA=true.Signed-off-by: CrazyMax crazy-max@users.noreply.github.com