Every pull request is different

Create a clear set of rules and policies that automates how code gets merged in your repo. Visible in the IDE, developers understand how their PR will be treated and how to follow the repo policy.

Common pull request process:

Every pull request is treated the same

Continuous Merge with gitStream:

Small changes - Auto-approve!
Common Change - Find the right reviewer
Critical change - requires 2 or more reviewers
Create your custom repo automations >

Coding is what you enjoy,
why is most of your time spent waiting?

Avg time to production 12 days
based on data from 1.1 million PRs from 1.6k different organizations

What is Continuous Merge (CM)?

​⁠Continuous Merge (CM) is the practice of improving merge efficiency by classifying pull requests based on change size and complexity. Automating the merge path based on the unique merge conditions allows work to flow more efficiently.

Why Continuous Merge?

Developers are often blocked from shipping code by a standard approval process. Unfortunately there is no such thing as a “standard” PR. Continuous Merge sets up automations so code that needs extra attention gets it, and everything else is expedited.

checks:
  content:
    is:
      only_docs: {{ files | allExtensions(['md', 'txt', 'rst']) }}

automations:
  approve_docs:
    if:
      - {{ checks.content.is.only_docs }}
    run:
      - action: approve@v1
Get Started

Small changes - Auto-approve!

Why wait on small changes? Applying an auto-approve check to pull requests with simple changes that don’t require indepth review speeds up your time to merge.

Small changes like text corrections, images or css that passed all tests shouldn’t require a full review process.

See documentation

Standard change -
Find the right reviewer

Coding changes that impact several files or areas still need a human review. Use gitStream to find a teammate who has the time and the skills needed to provide a quality review.

Create a rule that selects reviewers based on workload, review time and area of expertise. gitStream automation makes sure the right person is assigned so your PR gets picked up faster and merged with higher confidence.

checks:
  change:
    is:
      core_service: {{ files | includesRegex('core.*\.js$')  }}

automations:
  senior_review:
    if:
      - {{ checks.change.is.core_service }}
    run:
      - action: set-reviewer@v1
        args:
          - reviewer: @team-leader
Get Started
checks:
  code:
    is:
      secret_free: {{ source | gitLeaks | length > 0 }}

automations:
  double_review:
    if:
      - {{ ! checks.code.is.secret_free }}
    run:
      - action: set-required-reviewers@v1
        args:
          - reviewer: 2
      - action: add-labels@v1
        args:
          - labels: 
            - leak-detected
Get Started

Critical change - require a more specialized review

Some code changes are more sensitive, and need to be reviewed by principles or specialists. Create an automation that assigns a specific person or team to any code changes in that area of the codebase.

gitStream codifies the unwritten rules of your organization, turning communication and visibility into an automated task.

Cool, I want that! how do I get it on my repo?

for repo owners

Create your own rules by writing your repos .cm file

Instead of just a Readme.md or Contributors.md, create .cm files to communicate and enforce how changes are reviewed and merged as code. Our robust language of automations, checks, reviewers and more, allows you to describe how your team should interact with the repo.

learn more about .cm files
for devs

Get started with gitStream for Visual Studio Code

The fastest way to get started is to download and install our Microsoft Visual Studio Code Extension. This extension creates badges right in the description of the PR, telling the reviewer what was changed. In just a few clicks your code is ready for review.

coming soon
Sign up for developer newsletter: