Creates an attachment under a content reference URL in the body or comment of an issue or pull request. Use the id and repository full_name of the content reference from the content_reference event to create an attachment.
The app must create a content attachment within six hours of the content reference URL being posted. See “Using content attachments” for details about content attachments.
You must use an installation access token to access this endpoint.
The owner of the repository. Determined from the repository full_name of the content_reference event.
The name of the repository. Determined from the repository full_name of the content_reference event.
The id of the content_reference event.
The title of the attachment
<= 1024 characters
Example:Title of the attachment
The body of the attachment
<= 262144 characters
Example:Body of the attachment
Response
Content Reference attachments allow you to provide context around URLs posted in comments
The ID of the attachment
Example:21
The title of the attachment
<= 1024 characters
Example:Title of the attachment
The body of the attachment
<= 262144 characters
Example:Body of the attachment
The node_id of the content attachment
Example:MDE3OkNvbnRlbnRBdHRhY2htZW50MjE=
Enables an authenticated GitHub App to find the repository’s installation information. The installation’s account type will be either an organization or a user account, depending which account the repository belongs to.
You must use a JWT to access this endpoint.
Response
Installation
The ID of the installation.
Example:1
Any OfSimple User
Describe whether all repositories have been selected or there’s a selection involved
Allowed values:allselected
Example:https://api.github.com/installations/1/access_tokens
Example:https://api.github.com/installation/repositories
Example:https://github.com/organizations/github/settings/installations/1
Example:1
The ID of the user or organization this token is being scoped to.
Example:Organization
The permissions granted to the user-to-server access token.
Example:{"contents":"read","issues":"read","deployments":"write","single_file":"read"}
Example:config.yaml
Example:true
Example:["config.yml",".github/issue_TEMPLATE.md"]
Example:github-actions
Simple User
Example:"test_13f1e99741e3e004@d7e1eb0bc0a1ba12.com"
Lists installations of your GitHub App that the authenticated user has explicit permission (:read, :write, or :admin) to access.
You must use a user-to-server OAuth access token, created for a user who has authorized your GitHub App, to access this endpoint.
The authenticated user has explicit permission to access repositories they own, repositories where they are a collaborator, and repositories that they can access through an organization membership.
You can find the permissions for the installation under the permissions key.
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
You can find the permissions for the installation under the permissions key.
Installation
List repositories that the authenticated user has explicit permission (:read, :write, or :admin) to access for an installation.
The authenticated user has explicit permission to access repositories they own, repositories where they are a collaborator, and repositories that they can access through an organization membership.
You must use a user-to-server OAuth access token, created for a user who has authorized your GitHub App, to access this endpoint.
The access the user has to each repository is included in the hash under the permissions key.
Results per page (max 100)
Default:30
Page number of the results to fetch.
Default:1
installation_id parameter
The access the user has to each repository is included in the hash under the permissions key.
A git repository
Add a single repository to an installation. The authenticated user must have admin access to the repository.
You must use a personal access token (which you can create via the command line or Basic Authentication) to access this endpoint.
installation_id parameter
Response