Bug 205966 - Extend issue/bug automation from commit messages
Summary: Extend issue/bug automation from commit messages
Status: Open
Alias: None
Product: Services
Classification: Unclassified
Component: Bug Tracker (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Only Me
Assignee: Kubilay Kocak
URL:
Keywords: feature, needs-qa
: 213925 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-01-06 17:28 UTC by Mikhail Teterin
Modified: 2016-10-30 23:04 UTC (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mikhail Teterin freebsd_committer 2016-01-06 17:28:50 UTC
Very often an update from commit-hook is promptly followed by a separate update closing the bug.

I'd like to have the ability to change a bug's status through the commit message itself to save myself some work as well as reduce the amount of generated messages. Some development systems already use this and it is most convenient.

The exact syntax is up for discussion. I can think of two possibilities:

 1. Expand the semantics of the existing PR-field to also allow status changes.
    For example:
       PR: 1/closed, 2/inprogress
 2. Add a separate field to the commit template. For example:
       BZ: 1/closed, 2/inprogress

Ideally, the committing user's identity will also be used -- instead of the "commit hook".
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2016-01-06 17:37:46 UTC
We were just talking about this yesterday, and you'll see a reference to it in Mahdi's (cc'd) upcoming status report. Thanks for creating a issue for it :)
Comment 2 Jan Beich freebsd_committer 2016-10-30 23:04:10 UTC
*** Bug 213925 has been marked as a duplicate of this bug. ***