Skip to Content
We are conducting a survey to learn how startups, SMEs, developers, and technical teams currently host, deploy, and operate software. Take the survey
Infralane
Infralane
Workspaces and billingGitHub integration

GitHub integration

Connect GitHub at the workspace level to select repositories during application deployment.

Select the workspace

Use the workspace switcher and confirm the workspace name. The integration will belong to this workspace.

Open Integrations

Select Workspace → Integrations. The GitHub panel shows Connected or Not connected.

Start the connection

Select the GitHub connection action. A new GitHub window opens. Sign in to the intended account and review the requested access.

Limit repository access

When GitHub offers a choice, grant only the repositories the workspace needs. Follow your organization’s approval rules.

Return and verify

Return to Infralane and confirm the connected GitHub account or organization. Open the application deployment flow and verify that expected repositories are searchable.

Repository access can expose source code and enable deployments. Review access whenever team ownership changes, a repository is archived, or the workspace no longer needs the connection.

Repository not listed

Confirm the correct workspace is active, refresh the repository list, and check the GitHub App’s repository selection. An archived or disabled repository may appear unavailable. If the repository is public, you can use Public repository URL without selecting it from a connected account.

Disconnecting or changing access

Changing integration access can prevent new builds from reading a repository. Review dependent applications before revoking access. Keep a record of the change and verify repository selection afterward.

Never place a personal access token in a repository URL, environment-variable key, or support message.

Last updated on