Skip to content

Updates to the Checks Data Retention Policy

GitHub is updating the retention policy as it pertains to Checks data. Checks created by GitHub Actions and third-party GitHub Apps will be affected by the new retention policy.

Starting on February 14th, 2022 GitHub will begin archiving detailed checks data older than 400 days. As part of the archiving process we will create a rollup commit status representing the state of all checks for that commit. As a consequence, the merge box in any pull request with archived required checks will be in a blocked state and checks will need to be rerun in order to merge it.

Learn more about checks

While renewing GitHub Actions SSL certificates, an unexpected change in the intermediate certificate authority broke workflows using Open ID Connect (OIDC) based deployment to AWS.

To fix the issue please follow the following steps:

  1. In the AWS Console, go to IAM -> Identity Providers
  2. Open the provider(s) for
  3. Click Manage under Thumbprints
  4. Add the thumbprint 6938fd4d98bab03faadb97b34396831e3780aea1

We’re continuing to investigate, to ensure this issue does not reoccur in the future.

Learn more about using OIDC with GitHub Actions.

See more

New year, new GitHub Issues improvements! 🎉

We had several updates at the end of last year and are kicking off the new year with a number of improvements to the projects experience.

✅ Check in with reviewers

Many teams use reviewers to manage their pull requests, with our new field type – reviewers – any pull request added to your project will now display any assigned reviewers. Making it easy to see who’s been requested to review a pull request. To get started with reviewers:

  • Open the new field menu or the command palette and add the field reviewers to any of your existing views.
  • On the table this will display as a new column.
  • Or on the board this will display embedded in the card.
  • To keep the new field as part of your view, select save changes in the command palette or view menu.

The reviewers field is currently read only, with write access coming soon.


💙 Updated filter bar

It is now easier to see which filters have been applied to a view with our new tokenization in the filter bar, with filter criteria now displayed in blue and helpful error messages when no matches are found.


✨ Bug fixes & improvements

Other changes include:

  • Assignees are now always displayed in the side-panel for draft issues.
  • Bug fix for the selection behavior of multiple cards in the board layout. Previously clicking the ... menu would unselect all cards – making it hard to bulk remove multiple items.
  • The close button in the draft issue side-panel can now be navigated to with the tab key.
  • Bug fix so the filter -@current now includes items with no iteration – which is consistent with other negative filters.
  • When a board is pivoted by a value other than status, the status value can now be displayed as metadata on the card.

See how to use GitHub for project planning with GitHub Issues, check out what’s on the roadmap, and learn more in the docs.

See more