Intro
GitHub Enterprise is the on-premises version of GitHub.com . It makes collaborative coding possible and enjoyable for large-scale enterprise software development teams. GitHub Enterprise includes the same great set of features as GitHub. com but is packaged for running on your organization’s local network. All repository data is stored on machines that you control, and access is integrated with your organization’s authentication system (LDAP, CAS). Use GitHub Enterprise when you need complete control over repository and project information. You connect to your GitHub Enterprise account in the Data Center. This topic discusses the fields and menus that are specific to the GitHub Enterprise Connector user interface. General information for adding DataSets, setting update schedules, and editing DataSet information is discussed in Adding a DataSet Using a Connector.Prerequisites
To connect to your GitHub Enterprise account and create a DataSet, you must have the following:- A GitHub Enterprise username.
- A (properly scoped ) Personal Access Token
- The hostname to your GitHub Enterprise instance
Connecting to Your GitHub Enterprise Account
This section enumerates the options in the Credentials and Details panes on the GitHub Enterprise Connector page. The components of the other panes on this page, Scheduling, and Name & Describe Your DataSet, are universal across most connector types and are discussed in greater length in Adding a DataSet Using a Connector.Credentials Pane
This pane contains fields for entering credentials to connect to your GitHub Enterprise account. The following table describes what is needed for each field:Field | Description |
|---|---|
| Send PAT in authorization header as | Select how you would like to send the PAT in the Authorization header of the API calls. Github recommends using the Token -based Authorization header. |
| Hostname | Enter the hostname without ” http://” ” or ” https://” ”. Example: If the URL is https://xx.yy.zz.com , just type xx.yy.zz.com |
| Username | Type in the username for the account you’d like Domo to use to connect to your GitHub Enterprise instance. |
| Personal Access Token (PAT) | Type in the personal access token. When you create a personal access token , ensure you give it adequate scopes (permissions) for each report you want to run. |
Details Pane
This pane contains a primary Reports menu, along with various other menus which may or may not appear depending on the report type you select.Menu | Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Report | Select the GitHub Enterprise report you want to run. Make sure you grant your Personal Access Token (PAT) the necessary scopes for the reports you want to run. If you want to be able to run every report, you can use this link to create an access token with all of the necessary scopes : https:// YOUR_GITHUB_INSTANCE.com /settings/tokens/new?description=Domo%20GitHub%20Enterprise%20Connector&scopes=user,read:org,gist,repo,admin:org,admin:org_hook,admin:repo_hook,admin:public_key The following reports are available:
|
Available Permissions (Scopes):
Scopes are the set of permissions a Personal Access Token needs to be granted to allow the connector to create reports. Below is the list of scopes that are available:Name | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|
Repo | Grants full access to the public, internal and private repositories including read and write access to code, commit statuses, repository invitations, collaborators, deployment statuses, and repository webhooks. Note: In addition to repository-related resources, the repo scope also grants access to manage organization-owned resources including projects, invitations, team memberships, and webhooks. This scope also grants the ability to manage projects owned by users.
| ||||||||
admin:repo_hook | Grants read, write, ping, and delete access to repository hooks in public, private, or internal repositories. The
| ||||||||
| admin:org | Fully manage the organization and its teams, projects, and memberships.
| ||||||||
| admin:public_key | Fully manage public keys.
| ||||||||
| admin:org_hook | Grants read, write, ping, and delete access to organization hooks. Note: OAuth tokens will only be able to perform these actions on organization hooks that were created by the OAuth App. Personal access tokens will only be able to perform these actions on organization hooks created by a user. | ||||||||
| gist | Grants write access to gists. | ||||||||
| notifications | Grants: | ||||||||
| user | Grants read/write access to profile info only. Note that this scope includes user:email and user:follow.
|
Other Panes
For information about the remaining sections of the Connector interface, including how to configure scheduling, retry, and update options, see Adding a DataSet Using a Connector.FAQs
Does this connector require whitelisting or allowlisting?
Does this connector require whitelisting or allowlisting?
What version of the GitHub Enterprise API does this Connector use?
What version of the GitHub Enterprise API does this Connector use?
https://{yourdomain.com}/api/v3/).Which endpoint(s) does each report call in this Connector?
Which endpoint(s) does each report call in this Connector?
| Report Name | Endpoint URL(s) | |
|---|---|---|
| All Notifications | /notifications | |
| All Organizations | /organizations | |
| All Organizations (Advanced) | /stafftools/reports/all_organizations.csv | |
| All Private Feeds | /feeds | |
| All Public Events | /events | |
| All Public Gists | /gists/public | |
| All Public Repositories | /repositories | |
All Repo Comments | /repos/%s/%s/comments | |
All Repo Commits | /repos/%s/%s/commits | |
All Repo Issues | /repos/%s/%s/issues | |
All Repo Pull Request | repos/%s/%s/pulls | |
All Repo Pull Request Comments | repos/%s/%s/pulls/comments | |
All Repo Pull Request Reviews | null | |
All Repositories (Advanced) | /stafftools/reports/all_repositories.csv | |
| All Users | /users | |
All Users (Advanced) | /stafftools/reports/all_users.csv | |
| Authenticated User | /user | |
| Authenticated User Emails | /user/emails | |
| Authenticated User Issues | /user/issues | |
| Authenticated User Organizations | /user/orgs | |
| Authenticated User Repositories | /user/repos | |
| Authenticated User Starred Gists | /gists/starred | |
Company Productivity (All Repository Issues) | /repos/%s/%s/issues | |
Company Productivity (All Repository Pull Requests) | /repos/%s/%s/issues | |
| Gists Comments | /gists//comments | |
| Organization Details | /orgs/ | |
| Organization Issues - User | /orgs//issues | |
| Organization Members List | /orgs//members | |
| Organization Teams List | /orgs//teams | |
| Organization Webhooks List | /orgs//hooks | |
| Repository Events | /repos///events | |
| Repository Notifications | /repos///notifications | |
| Repository Stargazers | /repos///stargazers | |
| Repository Subscribers | /repos///subscribers | |
| Repository Issues | /repos///issues | |
| Repository Assignees | /repos///assignees | |
| Repository Issues Comments | /repos///issues//comments | |
| Repositories Issue Events | /repos///issues/events | |
| Repository Labels | /repos///labels | |
| Repository Milestones | /repos///milestones | |
| Repository Pulls | /repos///pulls | |
| Repository Contributors | /repos///contributors | |
| Repository Teams | /repos///teams | |
| Repository Languages | /repos///languages | |
| Repository Tags | /repos///tags | |
| Repository Branches | /repos///branches | |
| Repository Collaborators | /repos///collaborators | |
| Repository Comments | /repos///comments | |
| Repository Commits | /repos///commits | |
| Repository Contents | /repos///readme | |
| Repository DeployKeys | /repos///keys | |
| Repository Deployments | /repos///deployments | |
| Repository Downloads | /repos///downloads | |
| Repository Forks | /repos///forks | |
| Repository Merges | /repos///merges | |
| Repository Pages | /repos///pages | |
| Repository Releases | /repos///releases | |
| Repository Releases Latest | /repos/%s/%s/releases/latest | |
| Repository Statistics Code Frequency | /repos/%s/%s/stats/code_frequency | |
| Repository Statistics Contributors | /repos///stats/contributors | |
| Repository Statistics Commit Activity | /repos///stats/commit_activity | |
| Repository Statistics Participation | /repos///stats/participation | |
| Repository Webhooks | /repos///hooks | |
Search Code | /search/code | |
| User Followers | /users//followers | |
| User Following | /users//following | |
| User Keys | /users//keys | |
| User Organizations | /users//orgs | |
| User Repos | /users//repos | |
What kind of credentials do I need to power up this Connector?
What kind of credentials do I need to power up this Connector?
How often can the data be updated?
How often can the data be updated?
Are there any API limits I should be aware of?
Are there any API limits I should be aware of?
Troubleshooting
- Make sure your authentication remains valid.
- Review the configuration to make sure that all required items have been selected.
- Review the Connector history for error messages.
- In rare cases, you may be requesting too much information and reaching API limitations or timeouts. If this is the case, you can review the history of the Connector run to see the error message and duration. If this is the case, you can reduce the number of accounts that are being pulled, choose a smaller number of metrics for the report that you are pulling, or reduce the timeframe that you are trying to pull.