Explain that GITHUB_SHA may not always be the commit that was pushed#15482
Explain that GITHUB_SHA may not always be the commit that was pushed#15482ramyaparimi merged 7 commits intogithub:mainfrom
Conversation
|
@danielcompton |
|
Thanks @danielcompton - this makes sense to me. 👍 |
skedwards88
left a comment
There was a problem hiding this comment.
Thanks for this addition! I left a minor wording suggestion that I will go ahead an incorporate, then we'll get this merged down for you.
Automatically generated comment ℹ️This comment is automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
|
|
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:
Closes: #15302
What's being changed:
Check off the following:
Writer impact (This section is for GitHub staff members only):