GitHub and GitHub Enterprise configuration

github provides version control through an open source distributed version control system, which enables your entire codebase and history to be available to every developer and allows for easy branching and merging supports your use of github and github enterprise this topic describes the configuration requirements for both tools for to pull data from github, you must configure a github account pre requisites initial github configuration follow the steps in subsequent sections of this topic configure webhook to ensure proper data synchronization, you must configure webhook as part of the github integration click here for details github webhook configuration docid\ zq0j dl3dyubbeszvhd t integration of github with devops intelligence the process for onboarding github comprises the following steps, each of which is a multistep procedure create a personal access token create a connection configure the application onboard the github technical service create a github token the application requires the following information for github name local account name it could be any string and is used only for reference user username for github generally, the e mail id with which the user logged in to github token personal access token the personal access token requires permissions within the following recommended scopes the application also requires to set up permissions on github, navigate to the main page of the repository under your repository name, select settings → developer settings → personal access tokens → generate new token create a github enterprise token the application requires the following information for github enterprise name local account name it could be any string and is used only for reference host git api url of the git host eg, api url will take the form https //github domain com user username for github enterprise generally, the e mail id with which the user logged in to github enterprise token personal access token the personal access token requires permissions within the following scopes the application also requires the following github enterprise credentials gitendpoint github enterprise host https //github domain com name user's name user a user\@domain com token your personal access token create a connection before github and can exchange information, you must establish a connection between the two services use the following procedure click app manager → iam → connections → add new → add connection choose content provider as github provide a local account name for reference add the host git api url of the git host (e g , https //github test net ) enter your github account user name enter the token you created in the create a token section if you are using a proxy adapter, provide the proxyid uuid a proxy adapter is necessary when you want to access a service or system with a different interface than your application expects when sync is enabled, all organizations and repositories accessible to the user will be synced when archive is enabled, the connection is archived for future use secure alert synchronization pre requisites github personal access token token user needs to have secure alert access enabled for to pull data from github and github enterprise, you must provide the following permissions repository permissions on github, navigate to the main page of the repository under your repository name, select settings in the "security" section of the sidebar, select code security and analysis under "access to alerts", in the search field, start typing the name of the person or team you'd like to find, then select a name in the list of matches select save changes only one user credential can be used to pull information at a single time for a specific application this avoids reaching the ip rate limit for more information regarding secure alerts see secure alerts dasboard docid\ mrpffez9p f1wgundpsin for the github enterprise account if the administrator has set a limit on api calls, optimizes its process of fetching data and will take around 1000 calls each hour this is to make sure no other tasks using the credentials are hampered once the limit is exceeded we see a message depicting the same on sync page of github