ci: make commit sha consistent across workflows #680
Merged
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.
PR Checklist
Please check if your PR fulfills the following requirements:
What is the current behavior?
Issue Number: #671
Turns out what:
your-branch-commit
temporary-merge-commit
What is the new behavior?
The new behavior ensures that the commit SHA is consistent across different GitHub Actions workflows. This addresses scenarios in pull request workflows where GitHub creates a temporary merge commit, causing discrepancies between the local branch commit SHA and the one used in the GitHub Actions environment. As a result, the commit SHA will now reliably match between the local branch and the CI runtime, preventing inconsistencies and potential issues in the workflows.
Does this PR introduce a breaking change?
Other information