Monster Orange Get started

Monster Orange Den

Our GitHub Apps

For the person who installs them, usually a GitHub organization owner. Each App below lists every permission it asks for and why, what it never does, and how to remove it.

Monster Orange Den

Sign in to your own Den with GitHub, and send feedback as yourself.

Lets you sign in to the Den running on your computer with your GitHub account, from any browser, with no password. It also lets you file feedback from Den on GitHub in your name. It holds no key or secret, and never acts on your code.

Permissions

PermissionAccessWhy
IssuesRead and writeTo file the feedback you send from Den as an issue (or a comment on one) in your name.
MetadataReadRequired by GitHub for every App.

No account permissions. No webhooks or events.

What it never does

  • Never reads, changes or pushes code.
  • Never stores your GitHub token: each sign-in or report is approved on GitHub's own page, used once, and discarded.
  • Has no client secret and no private key (Den uses neither).
  • Never lets anyone but a Den's owner sign in to that Den.

Install and remove

Turn it off in Den
Set web.github_client_id: "". You then sign in with a one-time code or link instead.
Revoke it on GitHub
Settings › Applications › Authorized GitHub Apps › Monster Orange Den › Revoke.

About Den

Monster Orange CI runners

Runs a repository's CI jobs on its team's own test machines, one job per runner, then removes it.

Starts short-lived self-hosted GitHub Actions runners on test machines a team owns, only for repositories that opt in. Each runner takes one job and is removed. If a machine is busy, paused or off, jobs go back to GitHub's runners. It holds no secrets and never changes code.

Permissions

PermissionAccessWhy
Self-hosted runners (organization)Read and writeTo register a runner for one job, list runners, remove ones that are gone, and keep one runner group per repository (only that repository can use it).
ActionsRead and writeTo see which jobs are waiting, and to cancel and re-run a job when moving it back to GitHub's runners.
VariablesRead and writeTo set the one repository variable that sends jobs to the test machines, or back to GitHub's.
MetadataReadRequired by GitHub for every App.

No webhooks or events. No access to code, pull requests, issues or secrets.

What it never does

  • Never reads or changes code, never pushes.
  • Never reads Actions secrets (jobs that use production secrets stay on GitHub's runners).
  • Runs nothing for a repository that hasn't opted in: installing the App alone runs nothing.
  • Never runs a fork's pull request on the test machines.

Install and remove

Add a repository
The organization owner adds it to the App's installation (organization › Settings › GitHub Apps › Monster Orange CI runners › Configure › Repository access). Then the repository opts in by routing its jobs through its runner variable.
Remove a repository
Take it out of the installation. Its jobs go back to GitHub's runners.
Uninstall
Organization › Settings › GitHub Apps › Monster Orange CI runners › Configure › Uninstall. Every job runs on GitHub's runners again.

About Den

Monster Orange Den Hub

Your team's docs, design mocks and review comments, next to its code.

Den Hub is where a team's docs, design mocks and review comments live next to its code. It reads the repos you choose, so the team sees their issues, pull requests and Markdown docs in one place.

Permissions

PermissionAccessWhy
ContentsReadReads the Markdown (.md) files in the folders you choose, so docs show up in Den Hub. It never changes a file.
IssuesRead and writeReads issues so they appear in Den Hub. It writes in one case only: when a person in Den Hub files a report (a bug or a request), it opens one issue in the repo they pick, with the title and text they wrote. Automated agents can't do this.
Pull requestsReadReads pull requests so reviews and status show in Den Hub. It never comments, approves or merges.
MetadataReadRequired by GitHub for every App. It covers repo names and visibility.

No webhooks: it receives no events from GitHub and checks the chosen repos on a schedule.

What it never does

  • Never pushes code, edits or deletes files, or creates branches.
  • Never comments on, closes, labels or edits existing issues or pull requests.
  • Never approves or merges pull requests.
  • Never reads repos you didn't choose, or the contents of files outside the folders you set. (It lists a repo's file names to find the Markdown files in them.)
  • Never uses webhooks: it receives no events from GitHub.
  • Never touches organization settings, members, Actions, secrets or packages.

Install and remove

Install
An organization owner opens the install link from Den Hub, picks “Only select repositories”, chooses them, and installs. Den Hub then asks which company the install belongs to.
Remove
GitHub › your organization › Settings › GitHub Apps › Monster Orange Den Hub › Configure › Uninstall. You can also remove single repositories there. Den Hub stops reading at once.

See Den Hub

Questions before you install?

Ask us. We'll answer before you click anything.

Contact Monster Orange