---
schema_version: "1"
id: 731d9d1f2fd424e9bb1b1f010a34a421e6ee1343c9a5b5b4ed6b1a43a50efe9a
title: Set Up DevOps Center for GitHub
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/devops_center_configure.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.devops_center_configure.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7e7681e9763894370baf892e33d9f95eaa027e5c50c09bd33b9899920c235e97
description: To use GitHub with DevOps Center as your source control repository, some tasks are performed within GitHub, such as creating a repository and adding team members. And some tasks are performed in DevOps Center, such as setting up the associated DevOps Center project, adding development and pipeline environments, configuring your pipeline, and creating and assigning work items to team members.
products:
  - Salesforce Platform
release: "264"
---
# Set Up DevOps Center for GitHub

To use GitHub with DevOps Center as your source control repository, some tasks are performed within GitHub, such as creating a repository and adding team members. And some tasks are performed in DevOps Center, such as setting up the associated DevOps Center project, adding development and pipeline environments, configuring your pipeline, and creating and assigning work items to team members.

DevOps Center can be used with only GitHub.com Cloud-based plans, including GitHub Enterprise Cloud.

Here’s a sneak-peak at the overall process:

- Set up a [GitHub project repository](https://help.salesforce.com/s/articleView?id=platform.devops_center_setup_source_control_repos.htm&release=264.0.0&type=5 "A GitHub repository (sometimes called a repo for short) stores project work files — code, text, images, and so on. Each DevOps Center project needs its own repository for storing project changes. While you’re working on the project, the repository is the team’s centralized source of truth to manage changes.") and add team members as collaborators.
- [Set up your development and pipeline environments](https://help.salesforce.com/s/articleView?id=platform.devops_center_env_management_options.htm&release=264.0.0&type=5 "You have several options to manage your environments from the environment’s menu in the Pipeline Environments tab. Which menu options are available is determined by the environment type and whether the pipeline is activated.").
- [Create a GitHub Project](https://help.salesforce.com/s/articleView?id=platform.devops_center_create_projects.htm&release=264.0.0&type=5 "Create a GitHub project to help you and your team manage changes for a particular application or customization.").
- Plan, build, and activate your [pipeline.](https://help.salesforce.com/s/articleView?id=platform.devops_center_pipeline_build.htm&release=264.0.0&type=5 "After you define development environments and a release (production) org, you have a basic pipeline. However, it’s not recommended that you deploy directly to production. You can use our template to build the pipeline, you can add more stages to the pipeline template, or you can build your own.")
- [Create and assign project work items](https://help.salesforce.com/s/articleView?id=platform.devops_center_team_members_assign_work_items.htm&release=264.0.0&type=5 "Create work items so that when your team members open DevOps Center for the first time, project work is already identified and assigned to them.").
- Complete any optional setup tasks.

- **[Set Up Your GitHub Project Repositories](https://help.salesforce.com/s/articleView?id=platform.devops_center_setup_source_control_repos.htm&release=264.0.0&type=5)**  
    A GitHub repository (sometimes called a repo for short) stores project work files — code, text, images, and so on. Each DevOps Center project needs its own repository for storing project changes. While you’re working on the project, the repository is the team’s centralized source of truth to manage changes.
- **[Add Team Members to the GitHub Repo As Collaborators](https://help.salesforce.com/s/articleView?id=platform.devops_center_add_team_members_github.htm&release=264.0.0&type=5)**  
    In GitHub, add team members as repository collaborators. A collaborator is someone who has been granted write access to the project repository. Add everyone who creates customizations or code for your project to the project repository as a collaborator. That way, they have access to the repository through DevOps Center.
- **[If an Organization Owns the GitHub Repo](https://help.salesforce.com/s/articleView?id=platform.devops_center_org_owns_github_repo.htm&release=264.0.0&type=5)**  
    GitHub repos owned by an organization aren’t visible in DevOps Center until an organization account owner provides access.
- **[If the GitHub Organization Has an IP Allowlist](https://help.salesforce.com/s/articleView?id=platform.devops_center_ip_allow_list_org.htm&release=264.0.0&type=5)**  
    If you have restricted access to the GitHub organization assets by configuring an allowlist, add the domains for the DevOps Center app.
- **[Connect to a Different GitHub Account](https://help.salesforce.com/s/articleView?id=platform.devops_center_connect_diff_github_acct.htm&release=264.0.0&type=5)**  
    When creating or opening a project, all team members log in to GitHub using the account that has access to the repos that your team wants to use with DevOps Center. If you or a team member logged in with the incorrect GitHub account, a team member with Salesforce admin privileges can delete the authorization information so you or the team member can log in using the proper credentials.