Skip to content

Commit 50a2f7a

Browse files
authored
Improve notifications for developers involved in security campaigns #18872 (#57344)
1 parent 933b09b commit 50a2f7a

File tree

3 files changed

+3
-6
lines changed

3 files changed

+3
-6
lines changed

content/code-security/code-scanning/managing-code-scanning-alerts/best-practices-for-participating-in-a-security-campaign.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -38,10 +38,7 @@ Adopting a few key best practices can help you participate successfully in a cam
3838

3939
### Notification settings
4040

41-
To receive email updates about security campaigns in repositories you have write access to, make sure that you:
42-
43-
* **Watch** all repositories that you have write access to.
44-
* **Subscribe** to notifications for "All activity" or "Security alerts".
41+
You'll automatically receive email updates about security campaigns for any repositories you have **write** access to, so you can stay informed about relevant updates.
4542

4643
### View campaign details
4744

content/code-security/code-scanning/managing-code-scanning-alerts/fixing-alerts-in-security-campaign.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,8 +20,8 @@ topics:
2020
When a campaign targets security alerts in a repository that you have write access to, you can navigate to the list of repository alerts in the campaign.
2121

2222
* Display the **Security** tab for the repository and click one of the campaigns under "Campaigns" in the sidebar.
23-
* If you have enabled email notifications for "All activity" or "Security alerts" in the repository, click **View security campaign** in the campaign email.
2423
* If you have write access to more than one repository in the organization, display the **Security** tab for the organization and click one of the campaigns under "Campaigns" in the sidebar.
24+
* Alternatively, click **View security campaign** in the campaign's email notification.
2525

2626
This view shows the alerts in the current repository for a campaign called "SQL injection (CWE-89)" (highlighted gray) that is managed by "octocat" (outlined in dark orange).
2727

content/code-security/securing-your-organization/fixing-security-alerts-at-scale/creating-managing-security-campaigns.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -94,7 +94,7 @@ When you create a campaign, all the alerts are automatically submitted to {% dat
9494

9595
### How developers know a security campaign has started
9696

97-
When a campaign is started, anyone with **write** access to a repository included in the campaign, and has subscribed to watch either "All activity" or "security alerts" in that repository, is notified.
97+
When a campaign is started, anyone with **write** access to a repository included in the campaign is notified.
9898

9999
In addition to the automatic notifications sent out, the new campaign is shown in the sidebar of the "Security" tab for each repository included. For more information about the developer experience, see [AUTOTITLE](/code-security/code-scanning/managing-code-scanning-alerts/fixing-alerts-in-security-campaign).
100100

0 commit comments

Comments
 (0)