If you are an owner of an enterprise with GitHub Advanced Security, you can now enable secret scanning and push protection across your entire enterprise with only 1 click.
This new enablement setting also allows you to set a default custom link that will appear on a push protection block.
You can now express disinterest on rollup items in the "For you" feed to cater the feed towards your preferences. Get started by selecting "Show less activity like this".
This will prompt you to select more information about your preferences.
For questions and feedback, visit Community Feed Feedback.
API users can now integrate with a new dependabot_alert webhook, which matches the naming and structure of the recently introduced Dependabot alerts REST API. You should use this webhook in place of the existing repository_vulnerability_alert.
Improvements with the new webhook include:
read permission.created, dismissed, reopened, fixed, or reintroduced. See below for descriptions:| Action | Action definition |
|---|---|
created |
github has opened the Dependabot alert |
dismissed |
GitHub user dismissed the alert with dismissed_reason and an optional dismissed_comment |
reopened |
GitHub user manually reopened the previously-dismissed alert |
fixed |
github detected the Dependabot alert is resolved |
reintroduced |
github reopened the previously-fixed alert |
The repository_vulnerability_alert webhook is being deprecated. In 2023, we plan to remove the existing repository_vulnerability_alert webhook, which is superseded by the dependabot_alert webhook. We will give integrators at least 3 months notice of this removal — keep an eye on the GitHub Changelog in 2023 for more information.
Learn more about the Dependabot alerts webhook in our documentation.