Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

updated documentation #18

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

updated documentation #18

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
Auto-Merger
===========
.Auto merger combines the benefits of multiple branches and continuous integration. Auto merger “propagates” all commits performed on a repository. While propagating, it deduces by its configuration if a commit should be merged into further branches. If yes, it propagates the commit immediately from one branch to the next. During its operation it’s sending notifications to committers (and other predefined delivery list) to verify the correctness of merges performed on behalf of them. In case of failures (in most cases conflicts which requires a human to resolve) it will ask committer to resolve, merge, and then to confirm.
.
Auto-merger provides various reports to check backwards the merge-completeness status of branches. It’s filling up automatically an online spreadsheet, an audit file, and a web based online report which tries to detect separately from it’s actual merge operation, which merges were not verified or not done. All this, in order to assist querying the merge-health of branches.
Auto merger combines the benefits of multiple branches and continuous integration. Auto merger “propagates” all commits performed on a repository. <br>While propagating, it deduces by its configuration if a commit should be merged into further branches. If yes, it propagates the commit immediately from one branch to the next. <br> During its operation it’s sending notifications to committers (and other predefined delivery list) to verify the correctness of merges performed on behalf of them.<br> In case of failures (in most cases conflicts which requires a human to resolve) it will ask committer to resolve, merge, and then to confirm.
<br>
Auto-merger provides various reports to check backwards the merge-completeness status of branches. It’s filling up automatically an online spreadsheet, an audit file, and a web based online report which tries to detect separately from it’s actual merge operation, which merges were not verified or not done.<br> All this, in order to assist querying the merge-health of branches.

What?
=====
Expand Down