Skip to content

Instantly share code, notes, and snippets.

@jiito
Forked from ldez/gmail-github-filters.md
Last active June 24, 2022 16:40
Show Gist options
  • Save jiito/bc1376ef9632077f3ca79530e25fece3 to your computer and use it in GitHub Desktop.
Save jiito/bc1376ef9632077f3ca79530e25fece3 to your computer and use it in GitHub Desktop.
Gmail and GitHub - Filters

Gmail and GitHub

Create new filters and create new labels.

Pull Request

label: gh-pull-request

from:(notifications@github.com) subject:"PR \#" 

Note: special characters like ( or # are ignored and the escape \ doesn't work.

before 2021-10-11

from:(notifications@github.com) AND {"Patch Links" "approved this pull request." "requested changes on this pull request." "commented on this pull request." "pushed AROUND 1 commit" "pushed AROUND 2 commits"}

Requested Changes

label: gh-changes-req

from:(notifications@github.com) "requested changes on this pull request"

Merged

label: gh-pr-merged

from:(notifications@github.com) "Merged \#"

Approved

label: gh-pr-approved

from:(notifications@github.com) "approved this pull request"

Assignments

label: gh-assignments

from:(notifications@github.com) cc:(assign@noreply.github.com)

Mentions

label: gh-mentions

from:(notifications@github.com) cc:(mention@noreply.github.com)

Review Requested

label: gh-review-requested

from:(notifications@github.com) {cc:(review_requested@noreply.github.com) "requested your review on"}

GitHub emails

  • subscribed: The notification arrived because you’re watching the repository.
  • manual: The notification arrived because you’ve specifically decided to subscribe to the thread (via an Issue or Pull Request).
  • author: The notification arrived because you’ve created the thread.
  • comment: The notification arrived because you’ve commented on the thread.
  • mention: The notification arrived because you were specifically @mentioned in the content.
  • team_mention: The notification arrived because you were on a team that was mentioned (like @org/team).
  • state_change: The notification arrived because you changed the thread state (like closing an Issue or merging a Pull Request).
  • assign: The notification arrived because you were assigned to the Issue.
  • review_requested: The notification arrived because your review is required.

example:

Approximate rules

WARNING: Those rules can produce false-positives.

Closed (~)

label: gh-closed

from:(notifications@github.com) "Closed \#"

Note: special characters like ( or # are ignored and the escape \ doesn't work.

Merged (~)

label: gh-merged

from:(notifications@github.com) "Merged \#"

Note: special characters like ( or # are ignored and the escape \ doesn't work.

Issue (~)

label: gh-issue

from:(notifications@github.com) subject:("Issue \#" -"PR \#")

Note: special characters like ( or # are ignored and the escape \ doesn't work.

References

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment