Skip to content

Possibly incorrect examples for content attachments / content references #6823

@dtakahas

Description

@dtakahas

What article on docs.github.com is affected?

https://docs.github.com/en/rest/reference/apps#create-a-content-attachment

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

We have a GitHub App that creates content attachments and we received an email that the content_references URL path was changing to have the repository owner and repository name prefixed to it:

https://api.github.com/content_references/1512/attachments

becomes

https://api.github.com/OWNER/REPOSITORY/content_references/1512/attachments

The examples in the article appear to have been updated that way. However when I tried to update our app, I was receiving 404s. My colleague had a hunch and it began working again when we added the prefix /repos/ before the owner/repo part (e.g. https://api.github.com/repos/OWNER/REPOSITORY/content_references/1512/attachments)

Does that article possibly need to be corrected to have that prefix in the URLs?

Metadata

Metadata

Assignees

Labels

contentThis issue or pull request belongs to the Docs Content teamrestContent related to rest - overview.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions