Skip to content
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

"repository_dispatch" event shows wrong GITHUB.SHA and GITHUB.REF information #1494

Closed
ba32107 opened this issue Nov 20, 2020 · 1 comment · Fixed by #1493
Closed

"repository_dispatch" event shows wrong GITHUB.SHA and GITHUB.REF information #1494

ba32107 opened this issue Nov 20, 2020 · 1 comment · Fixed by #1493

Comments

@ba32107
Copy link
Contributor

ba32107 commented Nov 20, 2020

What article on docs.github.com is affected?

https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows#repository_dispatch

What part(s) of the article would you like to see updated?

The GITHUB_SHA and GITHUB_REF values seem to be wrong. As far as I can tell, there's no way to set a branch when triggering this event from the REST API. This presumption is also confirmed by the fact that the event has the following note:

Note: This event will only trigger a workflow run if the workflow file is on the default branch.

These values should both refer to the default branch. An example of what it should say:
https://docs.github.com/en/free-pro-team@latest/actions/reference/events-that-trigger-workflows#check_run

Additional information

I believe this was a copy-paste error from the workflow_dispatch event.

@welcome
Copy link

welcome bot commented Nov 20, 2020

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.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Nov 20, 2020
@janiceilene janiceilene removed the triage Do not begin working on this issue until triaged by the team label Nov 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants