Configuring Git

Name:
Local account name. It could be any string and is used only for reference.
User:
Username for Git. Generally, the login email ID.
Token:
Personal access token. Can be generated from the following:settings --> developer options --> personal access token.
Scope type
Name
Description
repo
repo:status
repo_deployment
public_repo
repo:invite
security_events
Full control of private repositories
write:packages
read:packages
Download packages from GitHub Package Registry
admin:org
read:org
Read organization and team membership, read organization projects
admin:repo_hook
read:repo_hook
Read repository hooks
admin:public_key
read:public_key
Read user public keys
write discussion
read:discussion
Read team discussions
user
read:user
user:email
user:follow
Update ALL user data
Provide repository permissions by navigating GitHub repository main page --> Settings --> Code security and analysis --> Access to alerts and typing the user's name in the search field, and click the correct user from the display list.

Name:
Local account name. Any string is valid; only for reference.
Host:
Git API URL of the Git Host. For example, API url such as https://github.abc.net/
User:
Username for GIT. Generally the email ID with which user logged in to Git.
Token:
Personal access token. Can be generated from the following: Settings --> developer options --> personal access token The personal access token requires the following permissions:
Scope type	Name	Description
repo	repo:status repo_deployment public_repo repo:invite	Full control of private repositories
admin:org	read:org	Read organization and team membership
admin:repo_hook	write: repo_hook read:repo_hook	Full control of repository hooks
admin:org_hook	admin:org_hook	Full control of organization hooks
notifications	notifications	Access notifications
write discussion	read:discussion	Read team discussions
admin:pre_received_hook	admin:pre_received_hook	Control enforcement of pre-receive hooks for an organization or repository
For both GitHub and GitHub Enterprise you must add a DevOps Intelligence connection.  Click Admin --> IAM --> Connections -->
Add New
button. Select
Add Connection
.

Name:
Local connection name. It could be any string and is used only for reference.
User:
Username for GIT. Generally the email ID with which user logged in to GIT.
Token:
Personal access token. Generated using the following: Settings --> access token The personal access token requires the API permissions

Name:
Local connection name. It could be any string and is used only for reference
Host
Git API URL of the Git Host. For example, API url such as https://github.abc.net/
User
Username for GIT. Generally the email ID with which user logged in to GIT
ProxyID:
(Optional) Use UUID for Proxy Adapter
Token:
Personal access token. Generate from settings --> access tokens The personal access token requires the API permission
For both GitLab and GitLab Enterprise you must add a DevOps Intelligence connection.  Click Admin --> IAM --> Connections -->
Add New
button. Select
Add Connection
.

Configuring DevOps Intelligence for Code QL, recent customers

Onboarding the Code QL technical service

Click the overflow menu for the selected application.
Select
Onboard Technical Service
. The service displays the Onboard Technical Service form.
Select
Static Scan
for
DevOps Phase
. The service displays the Tool Engine field.
Select
Code QL
for
Tool Engine
. The service displays the
Select Connection
field.
Select the appropriate connection. The service displays the
Select Organization
field.
Select the appropriate organization. The service displays the
Select Projects
field.
Select the appropriate project. The service displays the Repository Name field.
Select the appropriate repository.
Click
Onboard
. The service navigates to the Application Configuration page.
You now have the option of clicking the overflow menu for Develop and selecting
Edit/Delete Tools Configuration
to confirm that DevOps Intelligence has been fully configured for CodeQL.

Deleting Code QL as a technical service

Navigate to DevOps Intelligence →
Settings & Utilities
→
Application Configuration
.
Expand the application to view all associated phases.
Click the Overflow menu for
Secure
.
Click
Delete Technical Service
.
Click
Code QL
for
Select Tools Configured
. The service displays the
Select Organization
field.
Select the appropriate organization. The service displays the
Select Projects
field.
Select the appropriate project.
Click
Delete
.

Configuring DevOps Intelligence for Code QL, legacy customers