Add a git-ref parameter to specify checkout git reference #26
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
Co-authored-by: Brian Flad <bflad417@gmail.com>
bflad
reviewed
Jan 4, 2023
Co-authored-by: Brian Flad <bflad417@gmail.com>
|
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What?
This changes adds an optional git-ref parameter to both the Community and Hashicorp versions of the action. This allows users to optionally specify a specific branch, tag or SHA to checkout when using the Checkout Github Action. If this parameter is not used then the default behavior of using the reference or SHA that triggered the event or the default branch will be used.
Why?
This parameter is useful for release workflows that push changes to the repository and want to use this action in the same workflow. Since the default behavior is using the reference or SHA that triggered the workflow, if there is a change made to the remote during the workflow, it will not be captured during the checkout in this release action.