Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove periods from customizing-a-workflow-for-triaging-your-notifications #33932

Merged
merged 2 commits into from
Jul 11, 2024
Merged

Remove periods from customizing-a-workflow-for-triaging-your-notifications #33932

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0215713
Update customizing-a-workflow-for-triaging-your-notifications.md
devesh-2002 Jul 11, 2024
50b6b80
Merge branch 'main' into devesh-2002-patch-1
nguyenalex836 Jul 11, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions ...riaging-notifications/customizing-a-workflow-for-triaging-your-notifications.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,10 +27,10 @@ For an example workflow of removing notifications that are easy to remove or tri
Choose which type of notifications are most urgent to review and pick a time to review them that's best for you. You might consider the question "Who am I blocking?"

For example, you may decide to check your notifications in this order in the morning during your daily planning time:
* Pull requests where your review is requested. (filter by `reason:review-requested`)
* Events where your username is @mentioned, also called direct mentions. (filter by `reason:mention`)
* Events where a team you're a member of is @mentioned, also called team mentions. (filter by `reason:team-mention`)
* CI workflow failures for a specific repository. (filter by `reason:ci-activity` and `repo:owner/repo-name` and ensure you've enabled CI activity notifications for workflow failures in your notification settings)
* Pull requests where your review is requested (filter by `reason:review-requested`)
* Events where your username is @mentioned, also called direct mentions (filter by `reason:mention`)
* Events where a team you're a member of is @mentioned, also called team mentions (filter by `reason:team-mention`)
* CI workflow failures for a specific repository (filter by `reason:ci-activity` and `repo:owner/repo-name` and ensure you've enabled CI activity notifications for workflow failures in your notification settings)

{% tip %}

Expand Down
Loading