Git Integration for Skill Repositories

Max supports direct integration with Git repositories (GitHub and Bitbucket), allowing users to manage skill code via version control. This integration streamlines development workflows, ensures consistency across environments, and makes it easy to collaborate across teams.

Accessing the Git Integration

Navigate to the Skill Repositories section using the Git icon in the left-hand navigation bar. Here, you can view existing repositories or add a new one.

Adding or Editing a Repository

On the right-hand panel, you can configure repository details:

• Name
  A display name for the repository. This name appears in the left navigation list of repositories and also when viewing skills to be added to an Assistant.

• URL
  The HTTPS Git URL of the repository. For example:
  https://bitbucket.org/mycompany/template_skills.git

• Git Hosting Provider
  Select either GitHub or Bitbucket. This ensures proper handling of authentication and metadata.

• Checkout From
  Specify whether to pull from a Branch or a Tag. The integration supports fetching from any named branch (e.g., main) or tagged version.

• Branch or Tag Name
  Enter the name of the branch or tag to pull from. Common default is main.

• Repository Access Token
  Input a valid personal access token (PAT) for private repositories. This field is securely stored and masked for privacy. See BitBucket or Github documentation for gathering tokens. Read access to the repo is all that is required.

Syncing the Repository

Once the repository is configured and saved, click the Sync button in the bottom-right to pull the latest changes from the specified branch or tag. The sync process will:

• Fetch the latest code from the Git host
• Update the local skill definitions
• Track the sync status, including the last commit hash and timestamp

Example status message:
On main (cef0bd17 at 2025-06-03T18:45:50Z)

Migrating Between Environments

When an Assistant is migrated between environments (for example, from Staging to Production), its associated Git repository configuration is migrated along with it. This allows teams to maintain consistent skill references across environments.

However, the Repository Access Token must be manually re-entered after the first migration. This is a one-time step required to authenticate the repository in the new environment.

Important: Future migrations do not update the destination environment's repository configuration. This provides flexibility for different Git references per environment.

For instance, Production can be pointed at the main branch, while Staging can remain on a release-candidate branch. This enables controlled testing and promotion of skills through development lifecycles.