Large projects get a lot of pull requests. On busy projects, these pull requests can fall behind. The farther they fall behind, the less likely they become to ever get merged.
You’ve seen this for yourself. Pull request #6 on a project working on pull request #600, still open because it’s a good idea – just not quite good enough for anyone to do the tedious manual work of reconciling it with the master branch. Other common failure modes include delaying responding to merges with conflicts, or installing tools like “pager duty” to ensure rapid manual response to conflicts (see more in The life-cycle of merge conflicts).
“Tedious manual work”? A phrase to make any programmer’s ears prick up. There should be some way to automate that.
If a conflict happens, MergeResolver clones your repository and sets to work. First, it tries to avoid the conflict by retrying the merge, but on the Abstract Syntax Tree (AST) level.
By treating code as ASTs rather than simply a string of characters, MergeResolver recognizes code’s structure and semantics. This ensures all potential conflict resolutions will parse as valid code, and in some cases cleanly reconciles changes that would conflict under Git’s built-in, line-oriented merge algorithms (as in the above example).
If AST merging fails, things get more interesting. MergeResolver understands different strategies for reconciling merge conflicts – strategies mined from large datasets of real-world merge conflict resolutions (see On the nature of merge conflicts). With this knowledge it can generate possible conflict resolutions.
But how does it know which generated conflict resolutions are viable? MergeResolver relies on the only source of truth about a program’s requirements: its test suite. MergeResolver finds a viable resolution by looking for a resolution that passes your program’s test suite.
Once MergeResolver finds a resolution that passes your test suite, it uses GitHub’s Checks API to provide a button (under the Checks tab on the pull request) that can be used to accept the resolution.
If you want to inspect the conflict resolution before accepting it, a link is provided to a diff of the merge resolution commit.
Please let us know what works well or not for you, and we’ll strive to make it useful enough that it becomes a staple of your team’s development workflow.
This material is based upon work supported by the Defense Advanced Research Projects Agency (DARPA) under Contract No. D17PC00096. Any opinions, findings and conclusions or recommendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the Defense Advanced Research Projects Agency (DARPA); or its Contracting Agent, the U.S. Department of the Interior, Interior Business Center, Acquisition Services Directorate, Division III.
*** This is a Security Bloggers Network syndicated blog from Blog authored by GrammaTech Research. Read the original post at: https://blogs.grammatech.com/mergeresolver-automatic-merge-conflict-resolution