Skip to main content
The GitHub integration connects a Fluid theme to a repository branch. It gives your team a Git-backed workflow for reviewing theme files and tracking changes. The exact button labels can vary by account and integration state. Start from the Themes area and choose the action that connects a GitHub repository.

​
Connect a repository

1

Start the GitHub connection

In Themes, choose the GitHub connection action. Fluid opens GitHub’s authorization flow.
2

Authorize repository access

Install or authorize the Fluid GitHub App for the account or organization that owns your theme repository. Limit access to the repositories Fluid needs.
3

Choose a repository and branch

Return to Fluid and select the repository and branch that should back the theme.
4

Wait for the import

Fluid creates a theme and imports the branch in the background. Do not publish or edit the theme until the initial import finishes.
Each repository-and-branch connection creates a separate theme. Connect another branch when you need an independent preview or release workflow.

​
Work from GitHub

Make theme changes on the connected branch using your normal Git workflow:
  1. Pull the latest branch state.
  2. Create a focused branch for your theme change.
  3. Preview and test the theme locally.
  4. Review the change through a pull request.
  5. Merge it into the branch connected to Fluid.
After the connected branch changes, allow the synchronization to finish before you review the theme in Fluid. Confirm added, changed, renamed, and deleted files in the theme editor.

​
Work from Fluid

When the configured integration supports publishing back to GitHub, publishing a template in Fluid creates a corresponding repository change. Before using Fluid as the source of an edit:
  • Confirm you selected the expected theme and connected branch.
  • Pull or fetch the repository so you can see any new commit.
  • Review the generated diff before building another change on top of it.
  • Avoid editing the same file in Fluid and GitHub at the same time.

​
Use multiple connections safely

You can connect more than one repository or branch. Treat every connection as an independent deployment stream:
  • Give themes names that identify their repository and branch.
  • Keep production and preview branches distinct.
  • Verify the connected branch before publishing.
  • Remove repository access when a theme is retired.

​
Troubleshoot synchronization

If a change does not appear:
  1. Confirm the GitHub App can access the repository.
  2. Confirm Fluid is connected to the branch that received the commit.
  3. Check whether the initial import or a later synchronization is still running.
  4. Compare the GitHub commit with the files shown in Fluid.
  5. Reauthorize the GitHub connection if repository access changed.
For local theme development, see the Fluid CLI guide.