On Sat, Apr 23, 2016 at 2:06 AM, Steve Schow <st...@bstage.com> wrote:
>
>
> if so, not a big deal then, just have to use wrapper scripts to make sure
> to follow your work flow, always create a new branch on the first commit
> for any ticket. I will probably use a cookie or something to make sure
> while working on a ticket, all commits go to that branch, and tag the
> commit with the [nnnnnnnnnn] number as well.
>
We don't create a branch until an issue ticket has been reviewed,
investigated and approved.
Also, for us, almost all tickets are entered through the web interface.
Although Fossil's hooks feature works with tickets as well as with commits,
there is no mechanism to create a new branch from a hook script.
So, when a team member starts coding changes for an issue, she/he enters
the (wrapper) command:
fsl branch new BRANCH-NAME ISSUE-ID ?options?
then the wrapper script will create the new branch and tag it with the
issue ID as I described in a prior post,
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
