Git

Self-hosted Git repositories with pull requests, code review, CI/CD, and deep platform integration.

What Is Bosca Git?

Bosca Git is a full-featured, self-hosted Git server built directly into the Bosca platform. It provides the same core capabilities you would expect from services like GitHub or GitLab — repository hosting, pull requests, code review, branch protection, CI/CD pipelines, and webhooks — but running entirely within your own infrastructure, under your control.

Because Bosca Git is not a separate product bolted onto the platform, it can integrate deeply with other Bosca subsystems. Commits and pull requests automatically link to Work Ops tasks. Scripts and analytics queries can be sourced directly from Git repositories. Pipelines can trigger platform events that kick off content workflows, deployments, or notifications.

Key Capabilities

Capability	What It Does
Repository Hosting	Host standard Git repositories with S3-backed object storage. Repositories support visibility controls, merge strategy configuration, GPG enforcement, and content type classification.
Pull Requests	Propose, discuss, and merge code changes through a structured review process. Supports draft PRs, inline comments, reviewer verdicts, and multiple merge strategies.
Code Review	Reviewers can approve changes, request modifications, or leave comments. Inline annotations on specific diff lines enable precise, contextual feedback.
Branch Protection	Enforce quality gates on critical branches — require pull requests, minimum approvals, passing CI checks, linear history, and more.
CI/CD Pipelines	Automated build, test, and deploy workflows triggered by pushes, pull requests, tags, schedules, or manual dispatch. Results feed back into branch protection as status checks.
Webhooks	Deliver real-time HTTP notifications to external systems when Git events occur. GitHub-compatible payload format for broad ecosystem integration.
Forking	Create linked copies of repositories that share the parent's object store. Fork contributors can submit cross-fork pull requests back to the upstream repository.
Archiving	Mark repositories as archived to prevent new pushes while preserving all existing content. Archiving is fully reversible.

Deep Platform Integration

Bosca Git is not just a code hosting tool — it is woven into the broader platform in several important ways:

Work Ops auto-linking. When commit messages, PR titles, or branch names contain Work Ops task keys, the platform automatically detects them and creates bidirectional links. Your team can trace from a task to every commit and PR that contributed to it, and from any commit back to the task that motivated it.
Script and query sourcing. Platform scripts and analytics queries can be stored in and loaded from Git repositories. This means your automation logic and data queries benefit from version control, code review, and the full PR workflow.
Pipeline-triggered platform events. CI/CD pipelines can fire platform events upon completion — triggering content publishing workflows, cache invalidations, deployment steps, or notifications through the platform's event system.
Unified permissions. Repository access is managed through the same group-based permission system used across all of Bosca, so there is no separate user management layer to maintain.

Bosca Git is designed for multi-pod, stateless deployments. Repository data is stored in S3-compatible object storage, so Git server instances can scale horizontally without shared local disk.

Who Uses Bosca Git?

Developers push code, open pull requests, review teammates' changes, and monitor pipeline results.
Team leads configure branch protection rules, manage reviewer requirements, and oversee merge policies.
DevOps engineers set up CI/CD pipelines, configure webhook integrations, manage agents, and automate deployment workflows.
Product managers benefit from Work Ops integration — they can see which code changes relate to which tasks without leaving the platform.

Explore Git

Repositories — Create, manage, and configure Git repositories with S3-backed storage
Pull Requests — Propose, review, and merge code changes with structured feedback
Branch Protection — Enforce quality gates and access controls on critical branches
CI/CD Pipelines — Automated build, test, and deploy workflows triggered by Git events
Webhooks — Deliver real-time event notifications to external systems

If you are setting up a new project, start with Repositories to create your first repo, then read Branch Protection to lock down your main branch before the team starts pushing code.