Thus said Steve Schow on Fri, 22 Apr 2016 23:04:57 -0600: > 1 - step#4 is fine because dev is working on a branch. do you have any > mechanisms in place to prevent them from accidentally committing a > file on the trunk instead of the branch at this stage of the workflow?
There is nothing that prevents it, however, if they are already working on a branch, it is unlikely that it will be committed on trunk unless they first ``update'' or ``checkout'' trunk. But, even if they do, the gatekeeper can easily move the commit to a branch (as Richard mentioned) and fire off an email asking for clarification, or whatever. Also, if you want, you can always put some isolation between repositories. For example, the production build server may only be pushed to by the gatekeeper. Developers autosync to the ``public'' facing repository and this keeps things moving along, however, only after code review has happened by the gatekeeper does it get pushed from the gatekeeper's repository to the production. Also, keep in mind that the entire repository is pushed, so the gatekeeper would have to review *all* changes before pushing to the production build server. Andy -- TAI64 timestamp: 40000000571bcbc2 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
