Add workflow to output github.ref when the triggering event is a release #28
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
gonuke
reviewed
Aug 31, 2023
| uses: actions/checkout@v3 | ||
|
|
||
| - name: See what github.ref is on release | ||
| run: echo ${{ github.ref }} |
There was a problem hiding this comment.
maybe you want github.ref_name instead?
There was a problem hiding this comment.
Yep, I think that will work. I didn't consider it at first because it didn't have "release" in the description 😅
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.
This PR adds a short workflow called
releaseTest.ymlwhose purpose is to print out the value of the default variablegithub.ref. Although I mostly only care about the results when the event is arelease, I also made the workflow run onpull_requestandpushjust to see what the variable contains on those runs.After this PR is merged, I will create a new release on the
mainbranch to trigger this workflow to see whatgithub.refis when the triggering event isrelease.This PR was motivated by a recent PR on the PyNE repo where we have decided to integrate the name of releases as a tag for the latest image as well as the name of the virtual machine. While this test is not completely necessary, I think it's still a good idea to verify that our intended use of
github.refdoes work as we think it will, especially since the results can only be obtained after merging a PR and creating a release.