gh-not 🔕

GitHub rule-based notifications management

Install

• Download a binary from the release page.

• Install via gh:

  gh extension install nobe4/gh-not

  Is used with gh not, while the others gh-not. The documentation uses gh-not exclusively.

• Install via go:

  go install github.com/nobe4/gh-not/cmd/gh-not@latest

• Build from sources

  go build ./cmd/gh-not

Getting started

Run the following commands to get started and see the available commands and options:

gh-not --help
gh-not config --init
gh-not sync
gh-not list --filter '.author.login | contains("4")'
gh-not repl
...

How it works

gh-not fetches the notifications from GitHub and saves them in a local cache.

The synchronization between local and remote notifications is described in sync.go.

The sync command applies the rules to the notifications and performs the specified actions. It's recommended to run this regularly, see this section.

The other commands are used to interact with the local cache. It uses gh api-equivalent to modify the notifications on GitHub's side.

Configure

The configuration file contains the rules to apply to the notifications. Each rule contains three fields:

• name: the display name

• action: the action to perform on the notification

  The current list of action is found in actors.go.

• filters: a list of jq filters¹ to filter notifications with.

  Each filter is inserted into the following patter: .[] | select(%s).

  Each filter in the list is run one after the other, making it similar to joining them with and.

  It means that if you want to specify conditions with or, you need to write them directly in the filter.

  E.g.

  rules:
    - filters:
        - (.author.login == "dependabot[bot]") or (.author.login == "nobe4")
        - .repository.full_name == "nobe4/gh-not"

  Filters like:

  jq '.[] | select((.author.login == "dependabot[bot]") or (.author.login == "nobe4"))' | jq '.[] | select(.repository.full_name == "nobe4/gh-not")'

  See more at config.go and rule.go.

Automatic fetching

To automatically fetch new notifications and apply the rules, it is recommended to setup an automated process to run gh-not sync regularly.

E.g.

• cron

  0 * * * *  gh-not sync --config=/path/to/config.yaml --refresh --verbosity=4 >> /tmp/gh-not-sync.out 2>> /tmp/gh-not-sync.err

• launchd (macOS)

  <?xml version="1.0" encoding="UTF-8"?>
  <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
  <plist version="1.0">
    <dict>
      <key>EnvironmentVariables</key>
      <dict>
        <key>PATH</key>
        <string>/opt/homebrew/bin/:$PATH</string>
      </dict>
  
      <key>Label</key>
      <string>launched.gh-not-sync.hourly</string>
  
      <key>ProgramArguments</key>
      <array>
        <string>sh</string>
        <string>-c</string>
        <string>gh-not sync --config=/path/to/config.yaml --refresh --verbosity=4</string>
      </array>
  
      <key>StandardErrorPath</key>
      <string>/tmp/gh-not-sync.err</string>
      <key>StandardOutPath</key>
      <string>/tmp/gh-not-sync.out</string>
  
      <key>StartInterval</key>
      <integer>3600</integer>
    </dict>
  </plist>

  It is recommended to use https://launched.zerowidth.com/ for generating such Plist.

Footnotes

1. Technically, gojq is used. ↩