Last modified: 2014-03-09 01:14:46 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T64371, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 62371 - Gerrit should track follow-ups to a merged change (by commit SHA-1 and Change-Id), like CodeReview used to
Gerrit should track follow-ups to a merged change (by commit SHA-1 and Change...
Status: NEW
Product: Wikimedia
Classification: Unclassified
Git/Gerrit (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
: upstream
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-07 13:58 UTC by Bartosz Dziewoński
Modified: 2014-03-09 01:14 UTC (History)
11 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Bartosz Dziewoński 2014-03-07 13:58:53 UTC
Gerrit should track follow-ups to a merged change (by commit SHA-1 and Change-Id), like CodeReview used to.

Currently finding commit fixes, reverts or cherry-pick requires going through the comments (which are usually aplenty and mostly automated junk), if it was even mentioned in them, or doing some serious git archeology.
Comment 1 Bartosz Dziewoński 2014-03-07 14:46:18 UTC
(This was brought up by Emufarmers at http://lists.wikimedia.org/pipermail/wikitech-l/2014-March/074943.html .)
Comment 2 Tim Landscheidt 2014-03-09 01:14:46 UTC
Couldn't we abuse our Gerrit -> Bugzilla tool for that?  If a changeset A is uploaded and it contains something looking like a SHA1/Gerrit Change-Id in the commit message referring to changeset B, add a comment to B that links to A.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links