indygreg added a comment.
In https://phab.mercurial-scm.org/D3764#59425, @pulkit wrote: > Thinking out loud here: I see that `--dry-run` for rebase will be very useful for automation. How about returning 1 when there are conflicts and returning 0 when there are no conflicts? Also maybe we should add formatter support to the dry-run output for each command so that automation can read the JSON output and tell user what can happen. I approve of both of these feature suggestions! However, they should be implemented in standalone changesets and not incorporated into this one. REPOSITORY rHG Mercurial REVISION DETAIL https://phab.mercurial-scm.org/D3764 To: khanchi97, #hg-reviewers Cc: indygreg, pulkit, mercurial-devel _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel
