Setting up and using Keegi.
A sentence in, up to three colleagues out, each with one line of evidence from work they shipped. If nobody here has done it, Keegi says so.
LoadingSetting up and using Keegi.
A sentence in, up to three colleagues out, each with one line of evidence from work they shipped. If nobody here has done it, Keegi says so.
LoadingA sentence in, up to three colleagues out, each with one line of evidence from work they shipped. If nobody here has done it, Keegi says so.
An organisation installs Keegi and picks the repositories it may see. Keegi 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 Keegi, then which repositories the app may see. You need to be an owner of the organisation to install it.
If Keegi 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 Keegi may read. Archived repositories are not offered at all.
Disconnect removes the installation record here and deletes the pull requests Keegi read. It does not uninstall the app on GitHub, which is yours to do in your organisation settings.
Keegi 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:
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.