Integration
GitHub integration: work summaries and contributor tracking from your repositories
The GitHub integration connects your organization's repositories to OrgOrg for work summaries and contributor tracking. It reads who worked on what from commits, pull requests, and reviews, next to the people directory. Connected once for the org by an admin, and once per member for their own account.
What connects
- Repositories: the organization's repositories, read for commits, pull requests, and reviews.
- Contributors: each GitHub account matched to a person in the directory by email.
- Work summaries: what a person or a team shipped over a period, from the repository activity.
- Member connections: a person connects their own GitHub account to be matched to their work.
The apps that use it
How to set it up
- Connect the organization. In OrgOrg, go to Settings, then Connectors, and click Connect on the GitHub tile. GitHub asks which organization and repositories to authorize.
- Authorize the scopes. GitHub lists the permissions below. Confirm, and GitHub sends you back to OrgOrg.
- Each member connects their account. A person connects their own GitHub account from the same page, so their commits and reviews match their profile.
- Read the summaries. Work summaries and contributor activity appear for the people and the teams the repositories name.
The permissions it asks for
| Permission | What OrgOrg does with it |
|---|---|
| repo | Read the repositories, their commits, and their pull requests. |
| read:org | Read the organization's membership, to match accounts to people. |
| user:email | Read the email of an account, to match it to a profile. |
| repo:status | Read the status of a commit, as a pull request shows it. |
Frequently asked questions
- What does the GitHub integration do?
- It reads the organization's repositories for work summaries and contributor tracking. Who worked on what comes from commits, pull requests, and reviews, matched to the people in the directory. It writes nothing to the repositories.
- Which GitHub permissions does OrgOrg ask for?
- repo, read:org, user:email, and repo:status. They read the repositories, the organization's membership, the email of an account, and commit statuses. OrgOrg asks for no permission to write code or to manage the organization.
- Does each person need to connect GitHub?
- An admin connects the organization once. Each person then connects their own account so their commits and reviews match their profile; an account that no person claims shows as unmatched.
- Is the GitHub integration free?
- Yes. It comes with the suite, which is free for teams of up to 5 people.