[guardian-dev] git+redmine workflow idea for handling closing issues

[Steve Wyshywaniuk]

As a bit of info, outside of the git aspect that's how we are handling
storymaker tickets.
On Dec 11, 2013 8:17 AM, "Hans-Christoph Steiner" <hans at guardianproject.info>
wrote:

>
> So we can write "fixes #1234" or "closes #1234" in a git commit message,
> and
> the redmine issue tracker will parse that and respond accordingly.  The
> question that is still remains for me is whether "fixes #1234" or "closes
> #1234" should set the issue to Resolved or Closed.
>
> I was thinking for this workflow:
>
> https://guardianproject.info/2013/11/21/a-tag-team-git-workflow-that-incorporates-auditing/
>
> It might make sense to manually set the issue to Resolved once the person
> coding it thinks its done.  That person would then include "closes #1234"
> in
> the commit message.  Then after another dev on that project reviews the
> commit
> and pushes it to the main upstream git repo, redmine would get the commit
> and
> close the issue.
>
> .hc
>
>
> --
> PGP fingerprint: 5E61 C878 0F86 295C E17D  8677 9F0F E587 374B BE81
> _______________________________________________
> Guardian-dev mailing list
>
> Post: Guardian-dev at lists.mayfirst.org
> List info: https://lists.mayfirst.org/mailman/listinfo/guardian-dev
>
> To Unsubscribe
>         Send email to:  Guardian-dev-unsubscribe at lists.mayfirst.org
>         Or visit:
> https://lists.mayfirst.org/mailman/options/guardian-dev/steve%40smallworldnews.tv
>
> You are subscribed as: steve at smallworldnews.tv
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mayfirst.org/pipermail/guardian-dev/attachments/20131211/7d1b5525/attachment.html>