Setting up and using Ping&Bump

An organisation installs Ping&Bump and picks the repositories it may see. Ping&Bump then reads merged pull requests and builds cards for the people who wrote them. That is the one an admin sets up, and it is below.

A company that wants its own repositories read once, without connecting anything, sends a read-only token for named repositories and we run one export against it.

On /app/[org]/sources, press Connect GitHub. GitHub asks you to authorise Ping&Bump, then which repositories the app may see. You need to be an owner of the organisation to install it.

If Ping&Bump is not installed anywhere you administer, that button takes you to GitHub's install page. Install it there, come back, and press it again.

What you shared on GitHub is the ceiling. Every repository inside it starts off here, and you turn on the ones Ping&Bump may read. Archived repositories are not offered at all.

Disconnect removes the installation record here and deletes the pull requests Ping&Bump read. It does not uninstall the app on GitHub, which is yours to do in your organisation settings.

Ping&Bump stores no GitHub token for your organisation. It holds an installation number, and asks GitHub for a one-hour credential each time it reads.

For a company that wants its own repositories read once, without connecting anything. Merged pull requests from the repositories you name. Bots and open PRs are dropped. A repository the token can reach but you did not name stays unread.

Mint the token:

1. Open github.com/settings/personal-access-tokens/new. Fine-grained tokens. Not classic. Not a GitHub App.
2. Resource owner: you, or the organisation that owns the repos. If the org is missing from the list, it has blocked fine-grained tokens and somebody there has to allow them first.
3. Repository access: Only select repositories. Pick the ones you are sending. All repositories is the wrong grant.
4. Permissions: Pull requests, Read. Metadata comes with it. Nothing else. Generate, then copy it once. A week of expiry is enough.

Send us the token and the owner/name list. Do not paste them here, and there is no form on this page on purpose. We run the export and the token is never stored.