Open dimaqq opened 15 hours ago
Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.
Clarification:"
The difference is between on: pull_request
and on: pull_request_target
.
Thank you for raising this issue! I'll get this triaged for review :sparkles: Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/accessing-contextual-information-about-workflow-runs#github-context
What part(s) of the article would you like to see updated?
The ref given is fully-formed, meaning that for branches the format is
refs/heads/<branch_name>
, for pull requests it isrefs/pull/<pr_number>/merge
, and for tags it isrefs/tags/<tag_name>
. For example,refs/heads/feature-branch-1
.Additional information
Surely
github.ref
is notrefs/pull/<pr_number>/merge
for an outstanding pull request.My colleague tripped over reading this bit in https://github.com/canonical/operator/pull/1451