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

create webhook ref format incorrect #37014

Closed
1 task done
BeksOmega opened this issue Mar 20, 2025 · 2 comments
Closed
1 task done

create webhook ref format incorrect #37014

BeksOmega opened this issue Mar 20, 2025 · 2 comments
Labels
content This issue or pull request belongs to the Docs Content team fix-internally Triggers a workflow to copy the issue internally and close the current issue

Comments

@BeksOmega
Copy link
Contributor

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/webhooks/webhook-events-and-payloads#create

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

It says the ref property is "The git ref resource.", which links to https://docs.github.com/en/rest/git/refs?apiVersion=2022-11-28#get-a-reference which says the format is "ref": "refs/heads/featureA", in the example. Or possibly branch/<branch_name> or tag/tag_name. But when I test this, the format is actually just the branch/tag name, which no prefix.

Additional information

No response

@BeksOmega BeksOmega added the content This issue or pull request belongs to the Docs Content team label Mar 20, 2025
@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Mar 20, 2025
@Sharra-writes
Copy link
Contributor

Thanks for flagging this, @BeksOmega! I'll get this moved to be reviewed internally. 💛

@Sharra-writes Sharra-writes added fix-internally Triggers a workflow to copy the issue internally and close the current issue and removed triage Do not begin working on this issue until triaged by the team labels Mar 21, 2025
@docs-bot
Copy link
Collaborator

Thank you for opening this issue! Updates to this documentation must be made internally. I have copied your issue to an internal issue, so I will close this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team fix-internally Triggers a workflow to copy the issue internally and close the current issue
Projects
None yet
Development

No branches or pull requests

3 participants