GitHub Cloud
Shared Git User for Automatic Pushes
When auto-push is enabled, Tulip uses a shared GitHub user to push fetched changes. You will be prompted to authenticate with this user.
Please ensure that the shared GitHub user has admin permissions for the repository
Personal Git Credentials for Deployments
Each team member deploying to this environment must authenticate with their personal Git credentials.
If pull requests (PRs) are enabled:
The user must be able to create, update, squash, and merge PRs.
If PRs are disabled:
The user must have direct push permissions for the target branch.
You can configure squash and merge behavior in your repository under:
Repository Settings → General → Merge button section.
Troubleshooting
My repository does not appear in Tulip
After authenticating, your repositories might not immediately appear in Tulip. This is usually related to repository access configuration.
Tulip's GitHub app must be installed on your GitHub organization and have access to the repository you would like to connect.
Granting Repository Access to Tulip's GitHub App
Click “Resolve on GitHub” in Tulip.
This will open a GitHub page with your available organizations.
Select your organization to view Tulip’s app access settings.
Choosing Repository Visibility:
All repositories (Recommended) — grants access automatically for future repos.
Select repositories manually — choose the specific ones Tulip should access.
Once selected, click “Update Access”.
If you see a “Request” button instead, your GitHub admin must approve the request. Since GitHub email notifications are easy to miss, we recommend contacting your admin directly to expedite approval.
Once access is approved, you should see and select your repositories in the Tulip app.
My shared user keeps disconnecting
If you have set up a shared user and find the user goes missing or receives Invalid Credentials errors unexpectedly, please check under Settings / Developer settings / GitHub Apps / SaltoLabs and make sure that the option for User-to-server token expiration is not enabled. You may be opted-in to this setting by default.
GitHub Enterprise (On-Prem)
Requirements
You’ll need to register a GitHub App on your self-hosted GitHub Enterprise server.
Steps to Connect
Go to Version Control → GitHub → On-Prem.
Enter your GitHub Enterprise Server URL (e.g., https://your.git.server).
Do not include any repository path.
Click “Register GitHub App” in Tulip.
This opens GitHub Enterprise where you’ll configure your app.
Creating the App
Create a new GitHub App (e.g., named Tulip Labs).
Set the correct permissions as described in the Tulip UI.
Choose whether to install the app for all repositories or select specific ones.
After creation:
Copy the Client ID and Client Secret into the fields in Tulip.
OAuth Flow – Final Step
After completing the OAuth flow, if your repositories don’t appear:
Go to your GitHub Enterprise user settings → Applications → Install App
Locate Tulip Labs, click Install, and select your repositories
Once done, return to Tulip — your repositories should now be visible.
For questions or help with GitHub setup, contact support or reach out to your Tulip Customer Engineer.