Configuring DevOps Intelligence for GitHub, recent users

configure github for different devops phases and onboard the associated technical services configuration steps vary depending on the selected phase\ plan, develop, or secure this procedure is valid only for customers onboarded 6 june, 2024 or after procedures for legacy customers are provided in the subsequent section configure for github, legacy customers you must then onboard the technical service use the following procedures plan navigate to → settings & utilities → application configurations select an existing application or create a new application then add new tools → plan → add tool configuration → for tool engine select github complete the configurations, categorized in the four tabs release , work item format , bug formats , bug severity click add configuration develop navigate to → settings & utilities → application configurations select an existing application or create a new application then add new tools → plan → add tool configuration → for tool engine select github select the pull request states click add configuration secure navigate to → settings & utilities → application configurations select an existing application or create a new application then add tools → secure → add tool configuration → for secure categories select secure alerts → for tool engine select github fill the configurations, categorized into two tabs ( severity and state ) click add configuration github's dependabot alert is used in the secure phase, secure alerts category onboard the technical service you must now onboard the technical service use the following procedure navigate to → settings & utilities → application configurations click the overflow menu for the chosen application and click the onboard technical service option select the phase for which you want to configure github the page displays only the phases for which this tool has been configured for the application select the tool engine as github for connection select the appropriate connection name from the drop down supports the following types of github tracking organization repository non organization(independent) repositories use the following procedures organization tracking to track organizational data, use the following procedure select tracking type organization select the appropriate organization click onboard to onboard the technical service repository tracking to track repository level data, use the following procedure select tracking type repository select the appropriate organization for the repository the organization accounts will be listed select the appropriate repository a search box allows filtering repositories by name the selection of repos persists when the user navigates to the next page in the table click onboard to onboard the technical service in case of github enterprise accounts, if the administrator has set a limit on api calls, will optimize its data fetching process and will execute approximately 1000 calls each hour this is to make sure no other task using the credentials is hampered once the limit is exceeded, displays a message on github sync page non organization (independent) repositories to track non organization repositories, use the following procedure select tracking type repository (optional) select the appropriate repository click onboard to onboard the technical service deleting the technical service use the following procedure to delete the technical service navigate to → settings & utilities → application configurations expand the application to see all the associated phases click on overflow menu against the phase and click on delete technical service