Skip to content

Commit 8d4addf

Browse files
authored
Update README.md
1 parent 63ee7ce commit 8d4addf

File tree

1 file changed

+1
-14
lines changed

1 file changed

+1
-14
lines changed

README.md

+1-14
Original file line numberDiff line numberDiff line change
@@ -14,21 +14,8 @@ Found a bug? create a new item in the project's [issues](https://github.com/line
1414

1515
See the [automations](automations) direcotry
1616

17-
### Continuous Merge
17+
## Continuous Merge
1818

1919
**Continuous Merge (CM)** is the practice of automating the merge path by classifying pull requests based on change type, size, and complexity to allow work to flow more efficiently.
2020

2121
![Continuous Merge](assets/ContinuousMerge3l.png)
22-
23-
### How it works
24-
25-
Every time a dev opens a new Pull Request or changes a Pull Request, gitStream is triggered. Next, the `.cm` file is used to determine which automatic actions are invoked based on their conditions. The resulting actions use GitHub API to achieve the desired outcome.
26-
27-
The next steps are common practice of changing code in repo:
28-
29-
1. Create a feature branch
30-
2. Commit changes
31-
3. Push branch to remote repo
32-
4. Open Pull Request
33-
34-
See [examples](https://docs.gitstream.cm/examples/)

0 commit comments

Comments
 (0)