---
title: "Obtaining required GitHub information"
date: "2024-02-14T06:18:38+00:00"
summary: "Learn how to obtain the required GitHub information for the Cloud Platform Pipelines CLI. Get step-by-step guidance on finding your personal access token and setting the correct permissions for seamless repository connections."
image:
type: "page"
url: "/acquia-cloud-platform/obtaining-required-github-information"
id: "f697240b-7916-4897-bb1a-0aa2aead3c4b"
---

Use this page if you have questions about how to find the information the optional Cloud Platform Pipelines command-line client requires from GitHub during the [connection configuration process](/acquia-cloud-platform/features/pipelines/cli/github/connect). The following steps are not required to [connect through the user interface](../../connect.html).

Required GitHub permissions
---------------------------

To control the connection between a GitHub repository and the pipelines client, the user running the `pipelines github-connect` or `pipelines github-disconnect` command must have the proper permissions for the GitHub repository.

Git repositories can be owned by a user or an organization:

*   For repositories owned by a user account, the user running the  `pipelines github-connect` or `pipelines github-disconnect` command must temporarily be the owner of the user account. 
*   For repositories owned by an organization, the user must temporarily have the GitHub _Owner_ role in the organization owning the repository.

After creating the personal access token, the GitHub user no longer needs the _Owner_ role in GitHub. Therefore, you can revoke this role from the user without having an impact on the token.

For more information, see [What are the different access permissions?](https://help.github.com/articles/what-are-the-different-access-permissions/) in the GitHub help.

Obtaining your GitHub personal access token
-------------------------------------------

To use `pipelines github-connect` or `pipelines github-disconnect`, you must supply a GitHub personal access token. To retrieve your GitHub personal access token, complete the following steps:

1.  Sign in to your GitHub account.
2.  Change the settings for your GitHub profile by clicking your profile image in the upper right, and then click **Settings**.
    
    ![Accessing your settings](https://acquia.widen.net/content/0dkna89gly/png/pipelines_accessing-your-settings.png?crop=false&position=c&color=ffffffff&u=0b06mk&w=821&h=293)
    
3.  At the bottom of the left menu, in the **Developer settings** section, click the **Personal access tokens** link.
    
    ![Accessing personal acess tokens link](https://acquia.widen.net/content/dpa8ulmzsa/jpeg/pipelines_accessing-personal-access-tokens-link.jpeg?position=c&color=ffffffff&quality=80&u=bbviut)
    
4.  On the [Personal access tokens](https://github.com/settings/tokens) page, click **Generate new token** at the top of the page.
5.  In the **Token description** field, enter a description or name for your new token (such as `Cloud Platform`).
6.  In the **Select scopes** section, select the **repo** checkbox.
    
    ![Personal access token settings](https://acquia.widen.net/content/aem5kn6bbt/png/pipelines_personal-access-token-settings.png?crop=false&position=c&color=ffffffff&u=0b06mk&w=821&h=260)
    
7.  Scroll to the bottom of the page, and then click **Generate token**.
    
    ![Generating token](https://acquia.widen.net/content/uaazjkyqhg/png/pipelines_generating-token.png?crop=false&position=c&color=ffffffff&u=0b06mk&w=821&h=211)
    

The **Personal access tokens** page displays your new token, which is a string like `91a2b3c45d6f159ce524ac411e6d63b307e5ca93`. Since you can’t display the token again in the GitHub interface, copy the token and save it in a secure place.

You can then paste the token into the appropriate Pipelines command.

After creating the personal access token, the GitHub user no longer needs the _Owner_ role in GitHub. Therefore, you can revoke this role from the user without having an impact on the token.