Skip to main content
Repository access has two separate purposes: working on code in your chat and fetching code for shared environment builds.

​
Connect your personal account

Connect GitHub or GitLab through Replit’s integrations. Replit uses your authorized access to inspect code and, when requested and permitted, push branches and open pull or merge requests. Ask Replit:
For GitLab, replace GitHub with GitLab. Complete the connection flow and review the requested access. To connect from the interface, open Repositories and select Connect on the provider card. If it shows Manage, select Connect under Personal account. You can also connect through Integrations in your personal settings. Personal integrations showing GitHub and GitLab connection cards. Share the repository URL and confirm Replit can read it. Opening a pull request also requires permission to push a branch or use your team’s approved fork workflow. To disconnect your personal sign-in, return to Repositories > Manage and select Disconnect under Personal account. This does not remove the workspace’s repository grants.

​
Configure workspace access

A workspace administrator configures repository grants for background environment builds. Your personal sign-in does not replace this shared setup. Open Repositories, find the provider card, and select Manage. If the card shows Connect, sign in first. Under Workspace connection(s), choose Connect to sign in for workspace setup or Configure to manage existing access. Only workspace administrators can configure shared access. Members can view it and manage their own personal sign-in. Availability can differ by workspace.

​
GitHub: install and connect the app

  1. Sign in to GitHub in the workspace connection editor to see your organizations.
  2. Choose Add GitHub organization, then select the organization and repositories for the Replit GitHub App. Your GitHub administrator may need to approve it.
  3. Return to Replit, select Refresh if needed, and choose Connect beside the installed organization. Installation alone does not connect it to the workspace.
  4. Confirm the organization shows Connected before building an environment.
GitHub manages the installation’s repository permissions. If a repository is missing, review them with your GitHub administrator.

​
GitLab: connect a group

GitLab uses group and project grants, not a GitHub-style app installation.
  1. Sign in to GitLab in the workspace connection editor to see your groups.
  2. Choose Configure beside a group, select the projects to share, then choose Connect group.
  3. Confirm the group shows Connected. Use Edit to change the selected projects later.
If a group or project is missing, check your GitLab permissions and organization approval requirements.

​
Disconnect shared access

In Repositories > Manage > Configure, choose Disconnect for the workspace grant. This removes the workspace’s access through that grant, not your personal sign-in or the provider-side GitHub App installation. Builds and projects that rely on the grant lose repository access. Disconnecting a GitLab group also removes its Replit service account, memberships, and webhooks, and revokes existing build tokens. To remove only selected GitLab projects, use Edit instead. Removing projects revokes their workspace access and may invalidate existing build tokens.

​
Troubleshoot access

  • Chat cannot read or push: Check the connected personal account and its repository permissions.
  • Environment build cannot fetch code: Check the workspace connection and selected repositories.
  • App cannot reach a service: Repository access does not supply application credentials. See Add secrets to environments.
Never paste a personal access token into chat to work around an access error. After configuring shared access, continue to Create a reusable environment. External-service identities and chat secrets do not replace a workspace repository grant.