Skip to content

GitHub Actions: Re-run only failed or individual jobs

You can now re-run only failed jobs or an individual job in a GitHub Actions workflow run.

For more details see Save time with partial re-runs in GitHub Actions on the GitHub blog.

For questions, visit the GitHub Actions community

To see what's next for Actions, visit our public roadmap

View cache usage in your Action workflows

Dependency caching is one of the most effective ways to make jobs faster on GitHub Actions. You can now monitor the storage usage of your existing caches and get greater control over cache availability for your action workflows.

Actions users who use actions/cache to speed up their workflow execution times can now use our cache usage APIs to:

  • query the cache usage within each repository and monitor if the total size of all caches is reaching the upper limit of 10 GB,
  • monitor aggregate cache usage at organization level or even at enterprise level, if your GitHub organization is owned by an enterprise account.

Learn more about Managing caching dependencies to speed up workflows.

See more

Enable OAuth Device Authentication Flow for Apps

From today the OAuth Device Authorization flow feature must be manually enabled for all OAuth and GitHub Apps. This change reduces the likelihood of Apps being used in phishing attacks against GitHub users by ensuring integrators are aware of the risks and make a conscious choice to support this form of authentication.

If you own or manage an OAuth App or GitHub App that makes use of the OAuth Device Authorization flow, you can enable it for your App via its settings page:

Enable device flow

The OAuth Device Authorization flow API endpoints will respond with status code 400 to Apps that have not enabled this feature.

Learn more about the OAuth Device Authorization flow.

See more
View all changes