Link Search Menu Expand

Git Integration

Coming Soon — Git integration is currently in development. Contact us to be notified when it’s available.

Connect your Git repositories to ButterStack for seamless version control integration.

Table of contents

  1. Overview
  2. Prerequisites
  3. Setup Instructions
    1. Step 1: Navigate to Source Control
    2. Step 2: Configure Repository
    3. Step 3: Authentication Setup
      1. Option A: SSH Key (Recommended)
      2. Option B: Personal Access Token
    4. Step 4: Webhook Configuration
  4. Advanced Configuration
    1. Branch Protection
    2. Commit Message Parsing
    3. Asset Mapping
  5. Troubleshooting
    1. Common Issues
  6. Best Practices
  7. Next Steps

Overview

ButterStack integrates with Git to track asset changes, monitor commits, and streamline your development workflow. This guide will walk you through setting up Git integration for your projects.

🔄 Automatic Sync

Track commits and changes in real-time

🏷️ Smart Tagging

Automatically tag assets with commit info

📊 Change Analytics

Visualize asset evolution over time

Prerequisites

  • Git repository (GitHub, GitLab, or Bitbucket)
  • Admin access to your repository
  • ButterStack project created

Setup Instructions

Step 1: Navigate to Source Control

  1. Open your ButterStack project
  2. Go to Settings → Integrations
  3. Click Add Integration
  4. Select Git from the available options

Step 2: Configure Repository

Enter your repository details:

Repository URL: https://github.com/your-org/your-repo.git
Branch: main
Authentication: SSH Key or Personal Access Token

Pro Tip

Use SSH keys for better security and easier authentication management.

Step 3: Authentication Setup

  1. Generate an SSH key for ButterStack:
    ssh-keygen -t ed25519 -C "butterstack@your-domain.com"
    
  2. Add the public key to your Git provider:
    • GitHub: Settings → SSH and GPG keys
    • GitLab: Settings → SSH Keys
    • Bitbucket: Personal settings → SSH keys
  3. Paste the private key in ButterStack

Option B: Personal Access Token

  1. Generate a token with repository access:
    • GitHub: Settings → Developer settings → Personal access tokens
    • GitLab: Settings → Access Tokens
    • Bitbucket: Personal settings → App passwords
  2. Enter the token in ButterStack

Security Note

Tokens should have minimal required permissions. For GitHub, only repo scope is needed.

Step 4: Webhook Configuration

Enable real-time updates by setting up webhooks:

  1. Copy the webhook URL from ButterStack:
    https://app.butterstack.com/webhooks/git/YOUR_PROJECT_ID
    
  2. Add webhook in your Git provider:
    • GitHub: Repository → Settings → Webhooks → Add webhook
    • GitLab: Settings → Webhooks
    • Bitbucket: Repository settings → Webhooks
  3. Configure webhook events:
    • ✅ Push events
    • ✅ Pull request events
    • ✅ Tag push events

Advanced Configuration

Branch Protection

Configure which branches trigger asset tracking:

Protected Branches:
  - main
  - develop
  - release/*
  
Ignored Paths:
  - docs/
  - tests/
  - *.md

Commit Message Parsing

Enable smart parsing to extract metadata from commits:

Pattern: \[(TASK-\d+)\] (.*)
Extract:
  - Task ID
  - Description

Asset Mapping

Map file patterns to asset types:

Textures: "**/*.{png,jpg,tga,dds}"
Models: "**/*.{fbx,obj,gltf}"
Audio: "**/*.{wav,mp3,ogg}"

Troubleshooting

Common Issues

Connection Failed

Symptoms: “Failed to connect to repository”

Solutions:

  1. Verify repository URL is correct
  2. Check authentication credentials
  3. Ensure ButterStack IP is whitelisted (if applicable)
  4. Test connection with: git ls-remote <repo-url>
Webhooks Not Triggering

Symptoms: Changes not appearing in ButterStack

Solutions:

  1. Check webhook delivery logs in Git provider
  2. Verify webhook URL is correct
  3. Ensure webhook secret matches
  4. Check ButterStack webhook logs at Settings → Logs
Authentication Errors

Symptoms: “Authentication failed” errors

Solutions:

  1. Regenerate and update credentials
  2. Verify token permissions
  3. Check SSH key format (should start with ssh-rsa or ssh-ed25519)
  4. Ensure no extra whitespace in credentials

Best Practices

🔐 Security

  • Use SSH keys over tokens when possible
  • Rotate credentials regularly
  • Limit token permissions

📝 Commit Hygiene

  • Use descriptive commit messages
  • Tag releases consistently
  • Link commits to tasks

🗂️ Organization

  • Use branch naming conventions
  • Configure .gitignore properly
  • Keep assets organized by type

Next Steps



Back to top

Copyright © 2026 ButterStack. All rights reserved.