/:\ gitStream - LinearB
source link: https://linearb.io/gitstream/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Continuous Merge (CM) with gitStream is the next step in your CI/CD Pipeline
Just like code bases, not all PRs are equal. Continuous Merge lets you automate how code gets from the individual developer to the team branch with a clear set of requirements
Sign up for early access:
Coding is what you enjoy, but why is most of your time spent waiting?
What is Continuous Merge (CM)?
Continuous Merge (CM) is the practice of accelerating the pace in which code get merged by classifying pull requests – based on risk and complexity, and applying different (often fast approval and even automatic) merge lanes.
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 lanes and rules so code that needs extra attention gets it, and everything else is expedited.
Auto approve
Save time on waiting for reviewers by applying an auto-merge rule to your pull request when the changes you made in the code are simple and don’t require review. (for example: only images or css were updated, and the changes were tested and passed)
Add the right reviewer or multiple reviewers
Changes on more complex or sensitive code areas, or on service files need to be reviewed by the right people, field experts, or specific people who are familiar with the code. If it is a mission critical part of the program you more than likely need more than just one person, with gitStream, creating these rules is easy.
Cool, I want that! how do I get it on my repo?
gitStream 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. The VSC extension will speed up how quickly you can create meaningful pull requests, by reading your code and creating easy to read badges right in the description of the PR. Just a few clicks and you are ready for review.
gitStream for repo owners
Elite Users - write your your own .cm file!
With a robust language of lanes, gates, reviewers and more the .cm file allows you to describe to your team how they should interact with the repo. Instead of Readme.md or Contributors.md, which few read anyway, you can communicate and enforce how changes are reviewed and merged as code.
/:\ gitStream your PRs
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK