[guardian-dev] git+redmine workflow idea for handling closing issues
Nathan of Guardian
nathan at guardianproject.info
Thu Dec 12 09:45:12 EST 2013
On 12/11/2013 11:15 AM, Hans-Christoph Steiner wrote:
> 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.
I see "close" as not a development activity, but as a project manager
and/or QA activity. No activity from Git should ever result in a ticket
being closed. A human should manually do it after verifying the commit
does resolve the issue.
+n
More information about the Guardian-dev
mailing list