> For the complete documentation index, see [llms.txt](https://docs.codeocean.com/user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codeocean.com/user-guide/git-provider-integration-guide/setting-up-the-integration.md). # Setting up the Integration ## **Adding Git Credentials** In order to use the Git integration, you must first add credentials to your Account page in Code Ocean. 1. Click the Account icon 2. From the **Credentials** screen, click **+ Add Credentials** 3. Click **\ Credentials** 4. Enter your **Git provider's username** and a **Personal Access Token (PAT)**. Click the developer settings link to visit the webpage where a PAT can be generated. See below for more information.
{% hint style="info" %} If **\ Credentials** isn't an option under **+ Add Credentials**, please ask your Code Ocean admin to configure Git provider integration from the Admin Dashboard. {% endhint %} ## **Generate a Personal Access Token (PAT) for Code Ocean** Follow the steps below to generate a PAT in your Git provider's account. Note that the exact process varies depending on the Git provider, but the objective is to retrieve the token from the Git provider and add the token to your Code Ocean account. {% tabs %} {% tab title="GitHub" %} ### Creating a GitHub Personal Access Token 1. In the upper-right corner of the page, click your profile photo, then click **Settings**. 2. In the left sidebar, click **Developer settings**. 3. In the left sidebar, click **Personal access tokens**, select **Tokens (classic)**. 4. Click **Generate new token**, select **Generate new token (classic)**. 5. Fill out the form and check the **repo** box for the scope. ![](/files/X7XPBXdqVX5pBsIsYPVg) {% hint style="info" %} For more information about how to generate a GitHub PAT, read this [article from GitHub](https://docs.github.com/en/github/authenticating-to-github/creating-a-personal-access-token). {% endhint %} {% endtab %} {% tab title="GitLab" %} ### Creating a GitLab Personal Access Token You can create as many personal access tokens as required. 1. In the top-right corner, select your avatar. 2. Select **Edit profile**. 3. On the left sidebar, select **Access Tokens**. 4. Enter a name and optional expiry date for the token. 5. Select the [desired scopes](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html#personal-access-token-scopes). 6. Select **Create personal access token**. ![](/files/jW3ZNoJxOfrDrdKDt0n7) {% hint style="info" %} For more information about how to generate a GitLab PAT, read [this article from Gitlab](https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html). {% endhint %} {% endtab %} {% tab title="Bitbucket" %} ### Creating a Bitbucket App Password (equivalent to a PAT) 1. In the top right corner, select the Settings cog. 2. Select **Personal Bitbucket Settings**. 3. In the left menu bar, select **App passwords**. 4. Click **Create app password** and select at least read and write repository permissions. 5. Select **Create** to generate the access token.
{% hint style="info" %} For information about how to generate a Bitbucket PAT ("App Password"), read [this article from Bitbucket](https://support.atlassian.com/bitbucket-cloud/docs/create-an-app-password/). {% endhint %} {% endtab %} {% tab title="Azure DevOps" %} ### Creating an Azure DevOps Personal Access Token 1. Sign in to your Azure DevOps organization. 2. Open User Settings by clicking the icon in the top right of the screen and select **Personal access tokens**.
3. Select **+ New Token**. 4. Complete the required fields and choose the appropriate scope for the token. {% hint style="info" %} For more information about how to generate an Azure DevOps PAT, read this [article from Azure DevOps](https://learn.microsoft.com/en-us/azure/devops/organizations/accounts/use-personal-access-tokens-to-authenticate?view=azure-devops\&tabs=Windows). {% endhint %} {% endtab %} {% endtabs %} {% hint style="info" %} **Note:** If the email address you used to create your Code Ocean account does not match the email address associated with the GitHub account you've linked, commits will appear in GitHub as being created by a generic user with your Code Ocean user name. If you'd like commits from Code Ocean to appear in GitHub as being created by your linked GitHub account, you can simply add the email address used to create your Code Ocean account as an additional email address in your GitHub account by following this [guide from GitHub](https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-personal-account-on-github/managing-email-preferences/adding-an-email-address-to-your-github-account). {% endhint %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.codeocean.com/user-guide/git-provider-integration-guide/setting-up-the-integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.