Skip to Content
v1.33.6 · shipped One-screen report · Looks like your app Read the changelog →
Plugin marketplaceGitHub Issues

GitHub Issues plugin

Opens a GitHub issue for each bug Mushi Mushi triages, and closes it when the fix lands.

Setup (Mushi Mushi Cloud, no code)

  1. Create a fine-grained token with Issues: Read and write on the repo that should get the issues (it can be a separate public tracker repo).
  2. In the Mushi Mushi console: open the Integrations page, find GitHub Issues, and enter the owner, repo and token. Test connection checks it.

Mushi Mushi opens the issues and closes them itself; you do not need the npm package.

Self-hosted plugin

@mushi-mushi/plugin-github-issues does the same from your own server. The console’s Marketplace has no GitHub Issues listing, so you can’t install it from the console. On a Mushi Mushi server you run yourself, add a plugin_registry row for it and install it like any listed plugin.

npm i @mushi-mushi/plugin-github-issues export MUSHI_PLUGIN_SECRET=... export GITHUB_TOKEN=... # Issues: write, Metadata: read export GITHUB_OWNER=acme export GITHUB_REPO=widget-app npx -p @mushi-mushi/plugin-github-issues mushi-plugin-github-issues
EventAction
report.classifiedOpen an issue labelled mushi-bug (the label is created if missing)
fix.appliedClose the issue

The report → issue mapping is kept in memory unless you pass your own cache to createGithubIssuesPlugin(cfg, cache), so after a restart fix.applied can’t close issues opened before it.

Last updated on