What's new

What's new in Branchscope, most recent first.

Reviews and the code graph

  1. Conflict maps

    When the target branch has moved on, a change shows what each side changed since the merge base, element by element, and the semantic conflicts that merge cleanly as text.

  2. The review as a required check

    Each change's review is the check branchscope/review, which a ruleset can require before a merge. Only Branchscope can report it.

  3. The organization's Graph tab

    How an organization's services connect, with saved views and findings, as merged or as deployed.

  4. Connections between repositories

    A change lists your other repositories that call what it touches, and flags the callers it would break.

  5. Renames in reviews

    Moved and renamed code is recognised as such, and rules follow it.

  6. Reviews as diagrams

    Change maps, the API view, architecture and personal-data flow, drawn from the code graph.

Rulesets and the audit log

  1. Linear history and signed commits

    Rulesets can refuse merge commits and unsigned commits, and evaluate mode records what a ruleset would refuse before you enforce it.

  2. Audit log

    Who changed rulesets, secrets, mirrors, environments, webhooks and access, and when, for a repository, an organization or your own account.

  3. Tag rulesets and tag workflows

    Tags protected on every path, with Release tags covering v*, and workflows that run on: tag and on: release.

  4. Branch rulesets

    Who may update, delete or force-push a branch, and the changes, checks and deployments it needs first, with a bypass list.

Agents

  1. AI provider keys

    An installed agent app can run on your team's own key for Anthropic, OpenAI, Mistral or another provider, up to a monthly cap. Nobody can read the key back.

  2. Agent apps

    Delegate a change or a task to an agent; it posts status and replies in threads, and hears about tasks by webhook or MCP.

  3. MCP for agents

    Agents use repositories, changes, reviews and graphs as tools; every session and write is logged.

Actions and deployments

  1. Reviewers and wait timers

    Deployments to an environment can wait for one of its reviewers, then a timer. Agents can't approve, and by default nobody approves their own run.

  2. Identity tokens for jobs

    Jobs sign in to AWS, Google Cloud or Azure with short-lived OpenID Connect tokens instead of stored keys.

  3. Secrets

    Repository, organization and environment secrets for runs, encrypted and masked in logs. A run an agent set off gets none until a person approves it.

  4. Deployments and environments

    Jobs record what runs where, an environment can take only protected tags, and Deploy again rolls back.

  5. Releases

    A tag with a title and notes, drafts, and the change map since the previous release, its tag made through the push guard.

  6. Branchscope actions

    Workflows in the repository run on your own runners. Each job is a check a ruleset can require, and agents read the logs over MCP.

Integrations and the API

  1. Slack, Discord, Teams, Mattermost and Sentry

    Changes, reviews, runs, releases and deployments posted where your team talks, and releases with their commits sent to Sentry.

  2. Mirrors

    Every branch and tag pushed on to GitHub, GitLab or another git host, one way, with deletions and force pushes off unless you turn them on.

  3. OAuth apps

    Apps act for a person with their consent, or installed in an organization as themselves. MCP clients register themselves.

  4. API v1 and a TypeScript SDK

    A versioned REST API with an OpenAPI document, rate limits per token, and a typed client from the same schemas.

  5. Webhooks

    Every event, for a repository or a whole organization, signed to the Standard Webhooks spec and retried.

  6. Imports from GitHub and GitLab

    Bring a repository over once, with history, tags and open pull requests as changes, through the push guard.

Everyday work

  1. A stored default branch

    Each repository keeps its own default branch, which clones, the Code tab and rulesets follow. Changing it is recorded in the audit log.

  2. Forks and following

    Fork into your account or an organization; follow organizations and repositories, and hear about pushes, changes and failed runs.

  3. Chats

    Direct messages between two people, live and stored in the EU, with blocking.

  4. Squash, rebase, history and blame

    Squash and rebase merges, a commit's own page, a file's history, and blame.

  5. git over SSH

    Clone and push over SSH, with keys limited like tokens, including agent keys.

  6. The bscope CLI

    Browser sign-in, repos, changes, reviews and graphs from the terminal, with JSON and exit codes.