| Jun | JUL | Aug |
| 09 | ||
| 2019 | 2020 | 2021 |
COLLECTED BY
Collection: Save Page Now
Apps
GitHub Actions
GitHub Marketplace
Webhooks
Partnerships
REST API v3
GraphQL API v4
Blog
Forum
GitHub.com
GitHub Enterprise Server 2.21
GitHub Enterprise Server 2.20
GitHub Enterprise Server 2.19
GitHub Enterprise Server 2.18
gimenete
GitHub Actions is available with GitHub Free, GitHub Pro, GitHub Free for organizations, GitHub Team, GitHub Enterprise Cloud, and GitHub One. GitHub Actions is not available for private repositories owned by accounts using legacy per-repository plans. For more information, see GitHub's products in the GitHub Help documentation.
We've added two new endpoints to the GitHub Actions API that provide insight into the billable time used by your workflows.
The following endpoints are now available for you to use:
●Get workflow usage
●Get workflow run usage
We've released these endpoints into public beta. We may change aspects of these endpoints based on developer feedback.
If we do, we will announce the changes here on the developer blog, but we will not provide any advance notice.
If you have any questions or feedback, please let us know!
joshmgross
If a check run or suite is never started, you'll see the 
skipped conclusion. This is a common check run conclusion for GitHub Actions that have a job using an ifcondition.
We created the skipped conclusion to help distinguish this type of scenario from when a check run or suite is cancelled. A check run or suite has the cancelled conclusion when the check run was planned or started but then stopped. For example, a conclusion can be cancelled due to manual intervention or possibly some service issues that cause the check run to stop.
tarebyte
Before you could suspend a GitHub App, if an organization admin or user wanted to temporarily block an app's access to their repositories' resources, they could only uninstall the GitHub App completely. This has been particularly challenging for large organizations that may need thousands of people to reauthorize an app.
Now you can suspend a GitHub App's access to your resources for as long as you need and unsuspend the app's access when you're ready. When you suspend a GitHub App you've installed, the app cannot access your resources, the GitHub API, or webhook events.
You can suspend or unsuspend your GitHub App installation on GitHub through your app settings or using these REST API endpoints.
●PUT /app/installations/:installation_id/suspended
●DELETE /app/installations/:installation_id/suspended
Before people can suspend a GitHub app installation, the GitHub App owner must opt-in to the beta release. For more information, see "Suspending a GitHub App installation."
jakewilkins
Starting today owners of GitHub Apps can choose to have their user-to-server access tokens expire after 8 hours. Expiring user-to-server access tokens help to enforce regular token rotation and reduce the impact of a compromised token.
You can opt-in to this security feature in your App's Settings page under the Beta Features tab.
Once enabled, GitHub will provide a refresh token when your app creates a user-to-server token.
{
"access_token": "accesstoken",
"expires_in": "28800",
"refresh_token": "r1.refreshme",
"refresh_token_expires_in": "15811200",
"scope": "",
"token_type": "bearer"
}
POST /login/oauth/access_token HTTP/1.1
Host: github.com
grant_type=refresh_token
refresh_token=r1.refreshme
&client_id=xxxxxxxxxx
&client_secret=xxxxxxxxxx
jamesmartin
●
jakewilkins
We are announcing the deprecation plan of the previously deprecated "Create an installation access token" endpoint: POST /installations/:installation_id/access_tokens.
The supported replacement endpoint is named consistently with other GitHub Apps API endpoints and has been available since 2018.
POST /app/installations/:installation_id/access_tokens
If you have any questions or feedback, please let us know!
jakewilkins
●
jamesmartin
We are announcing the deprecation of two legacy GitHub Apps-related webhook events:
●integration_installation
●integration_installation_repositories
These events have been undocumented for some time and will be removed on the following timeline.
integration_installation and integration_installation_repositories events will no longer be sent after October 1 2020.
integration_installation and integration_installation_repositories events with the new events:
●installation
●installation_repositories
If you have any questions or feedback, please let us know!
Oneill38
We are expanding support for the triage and maintain permissions in the REST API. Users with the triage or maintain permissions can now use endpoints that reflect what they can do in a repository, such as adding a label to an issue. Additionally, these new permissions can now be granted and managed via the API and will show up as assigned roles in API responses.
For more information about these roles, see "Repository permission levels for an organization" in the GitHub Help documentation.
POST /repos/:owner/:repo/issues/:issue_number/labels
●DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name
●POST /repos/:owner/:repo/issues/:issue_number/assignees
●DELETE /repos/:owner/:repo/issues/:issue_number/assignees
●POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers
PUT /repos/:owner/:repo/topics
●PUT /repos/:owner/:repo/interaction-limits
●All of the endpoints that you can use with the triage permission role:
●POST /repos/:owner/:repo/issues/:issue_number/labels
●DELETE /repos/:owner/:repo/issues/:issue_number/labels/:name
●POST /repos/:owner/:repo/issues/:issue_number/assignees
●DELETE /repos/:owner/:repo/issues/:issue_number/assignees
●POST /repos/:owner/:repo/pulls/:pull_number/requested_reviewers
PUT /repos/:owner/:repo/collaborators/:username
●GET /repos/:owner/:repo/invitations
●PATCH /repos/:owner/:repo/invitations/:invitation_id
●GET /user/repository_invitations
●GET /orgs/:org/teams/:team_slug/repos/:owner/:repo
●PUT /orgs/:org/teams/:team_slug/repos/:owner/:repo
●GET /orgs/:org/teams/:team_slug/repos
skalnik
●
jpemberthy
Some API previews have graduated and are now an official part of the API. These preview headers are no longer required.
gambit preview graduates
gambit preview.
application/vnd.github.gambit-preview+json
shadow-cat preview graduates
shadow-cat preview.
application/vnd.github.shadow-cat-preview+json
mscoutermarsh
The Actions API is now generally available and out of Beta! For more information about this API, see the "Actions API."
Thank you to everyone who tried out this API and provided feedback during the beta period.
GitHub Actions is available with GitHub Free, GitHub Pro, GitHub Free for organizations, GitHub Team, GitHub Enterprise Cloud, and GitHub One. GitHub Actions is not available for private repositories owned by accounts using legacy per-repository plans. For more information, see GitHub's products in the GitHub Help documentation.
ahoglund
We are temporarily removing access to GraphQL Explorer so we can improve how it works in different browsers.
The downtime is scheduled for:
●March 20, 2020
●From 3:00 PM UTC - 5:00 PM UTC
We apologize for any inconvenience during this time.
1
2
3
…
30
31