On Mon, Aug 3, 2015 at 6:33 PM, Andy Goth <[email protected]> wrote: > > Maybe split this functionality from the commit command and make a new > warning or audit or check command which will print all the things that > may prevent a commit from going forward, but also toss in extra files if > the check-extras setting is enabled. >
I think this would be a useful feature. Currently, in the pre-build section of our main build script, we test the output of "fossil extras" to make sure it's empty. If not, the captured output is displayed and the build aborted. Then after a successful build, the changes are committed and tagged with the build ID. If Fossil had a a command to perform the pre-commit checks, then "commit blockers" could be resolved before the actual build.
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
