-
Notifications
You must be signed in to change notification settings - Fork 64.8k
Clarification of the github context variables github.ref and github.ref_name
#41375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
github.ref and github.ref_name
|
@PabloCollazoCollarte Thanks for the PR! I will take this one to the team and let you know. |
This comment was marked as spam.
This comment was marked as spam.
|
@PabloCollazoCollarte After looking this over more carefully, I'm inclined to approve it. It's fairly minor and even if you're wrong (which I doubt) it should be easy enough for people to see where the problem is, and someone will probably come correct it. I'll get this added to the merge queue once the checks are passing. |
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
Why:
github.refandgithub.ref_nameinformation was a little bit misleading, since if a pull request is merged, the value of this variables will be the head branch, notrefs/pull/<pr_number>/merge.Closes:
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following: