Skip to content

Secret scanning now runs a historical scan to detect newly added secret types

GitHub will regularly run a historical scan to detect newly added secret types on repositories with GitHub Advanced Security and secret scanning enabled.

Previously, customers could manually trigger a historical scan to detect new secret types by re-enabling secret scanning, e.g. clicking "Enable all" at the organization level. Now, historical scans are automatic; customers can expect an email of any new detections in their repositories, just like they would when first enabling secret scanning today.

The new Scheduled Reminders UI

We made significant enhancements to schedule reminders experience in GitHub app for Microsoft Teams.

  • We have introduced a first class UI to configure your pending pull request reminders. And as part of this UI, we added a bunch of advanced controls that will help you in fine tuning your reminders.
  • We relaxed the administrator requirement to configure reminders. Now, any contributor can schedule reminders in MS Teams for the repositories he/she has access.

This will ensure you get reminders for the pull request that need your attention and there is no unnecessary noise in the channel.
Learn more about schedule reminders here.

Issue card updates

We made few more improvements to the issue notifications experience.

  • Introduced issue comment, close/reopen capabilities in GitHub personal app.
  • Made few updates to the look and feel of the GitHub issue notification card.

For more information visit the GitHub app guidance for Microsoft Teams.

See more

We've made exciting design improvements to GitHub Actions to promote better discoverability and accessibility. The improvements include:

  • An improved navigation experience that makes it easier to search workflows and workflow runs.
  • Added structure to better represent the hierarchy between caller and called reusable workflows.
  • A better mobile experience that is more consistent and supports multiple viewports.

Workflow run

For questions or to share your feedback, visit the GitHub Actions community.

See more