Every pull request is unique

gitStream lets you configure rules that decide how each pull request is treated based on the content of the code. These rules automatically find the right reviewer, check for deprecation, add context tags, and much more.

Read docs >>

Common PR process:

Every pull request is treated the same

Continuous Merge with gitStream:

Find the right

Skip the wait times
and improve your developer experience

πŸ˜€ 1 day Coding 😑 2 days PR pickup 🀬 5 days PR review πŸ˜€ 1 day deploy
πŸ˜€ 1 day Coding 😑 2 days PR pickup 🀬 5 days PR review πŸ˜€ 1 day deploy

Continuous Merge (CM)

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.

Learn More >>
- action: add-label@v1 
    label: "{{ est_review_time }} min review" 
    color: {{ 'E94637' if (est_review_time >= 20) else '36A853') }}
Get Started

Empower developers
with PR info

Pull requests are a black box for the reviewer. What ticket is this for? How long is this going to take?

gitStream adds context to your PRs with labels and comments. This added context empowers your developers to make the best decisions about how and when to work.

Learn how to add a Review Time label to your PRs >>

Let gitStream
assign the best reviewer

Ensure the highest quality review possible by automatically assigning the best reviewer for each PR.

Sensitive code - Expert Reviewer
Security Risk - 2 Reviewers, 1 from DevSec
General PR - 1 Sr. Dev, 1 Jr. Dev for Knowledge Sharing

gitStream can analyze the activity and content of your code to assign the right reviewer by looking at the history, work load, git blame and more.

Learn how to automate reviewer assignment >>
- action: add-reviewers@v1 
    reviewers: {{ repo | rankByGitBlame(gt=25) }}
  - {{ files | allDocs }}
  - action: add-label@v1
      label: safe-changes
  - action: approve@v1
Get Started

Automate change requests and PR approvals to save time

Speed up time to merge by applying an auto-approve check on pull requests with simple changes like minor version updates of internal libraries.

Change Requests
Automate change requests based on org. level coding practices like moving away from deprecated services.

Learn more about automating best practices >>

Create your own rules
by writing your own .cm files

Instead of 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, and reviewers, allows you to customize how your team should interact with the repo.

Read the docs on creating your first .cm >>

Surviving SVB’s Collapse & Outsmarting Uber
Join our Dev Interrupted Livestream with Kyte’s Head of Product and Engineering, Nick Cobb