7327 2015-02-16 17:38:23 +0000 Add git hook to update bug status 2024-11-14 16:22:00 +0000 1 1 5 Infrastructure Bugzilla bugzilla unspecified x86 Multiple NEW https://bugzilla.yoctoproject.org/show_bug.cgi?id=9817 Medium enhancement Future 1 michael.g.wood ross.burton alex.kanavin bluelightning infras.bug.watcher Infras.watcher mhalstead randy.macleod richard.purdie ross.burton --- --- No (bug/feature does not impact docs) oldest_to_newest 48870 0 michael.g.wood 2015-02-16 17:38:23 +0000 I'd be useful if bug status were automatically updated once the patch is in tree. Not just because it's time saved updating bug status but also for the value in the email notification generated for QA fixer. It should be fairly easy to scrape the commit message body for [YOCTO #nnnn] and then the bug number parsed. Various tools exist to update the bug status such as pybugz http://www.liquidx.net/pybugz/ 48932 1 bluelightning 2015-02-19 15:48:00 +0000 The consensus is that we wouldn't want to mark bugs resolved automatically, however we should be at the very least adding a comment to the bug with a link to the commit. Richard raised another concern that this should not impose additional time on his process of pushing changes, so it would have to be either completely independent of the pushing client, or a process that simply gets triggered at the end of pushing and asynchronously does the bugzilla updates on a server somewhere. 56605 2 bluelightning 2015-11-18 22:24:16 +0000 We may do this from patchwork rather than from a separate script, since that's already triggered when commits are pushed to the git repository. 69728 3 ross.burton 2017-01-11 17:19:44 +0000 I was reminded about this by looking at a bug in glibc, which does comment in bugs when a commit references the bug. As we agreed it doesn't do anything apart from leave a comment: https://sourceware.org/bugzilla/show_bug.cgi?id=20019#c14 Gitzilla (https://github.com/gera/gitzilla) appears to make this fairly simple, and the reminder that a patch has landed will be very useful to ensure bugs are closed and alert users that their bugs are resolved. Is there any chance we can get this done sooner rather than later? 82124 4 mhalstead 2018-11-09 15:30:32 +0000 Would you expect the bugzilla entry to be similar to the sourceware comment you linked to? 82128 5 ross.burton 2018-11-09 15:47:55 +0000 Yes, similar, the commit log and patch summary would be good to help identify what landed. 88561 6 ross.burton 2020-11-05 08:10:57 +0000 *** Bug 9817 has been marked as a duplicate of this bug. *** 94400 7 randy.macleod 2022-11-10 15:55:57 +0000 A script rather than a git hook is what people prefer. Ross claims to have a starting point. 94401 8 ross.burton 2022-11-10 15:57:57 +0000 So some time ago I wrote a little script that looks through the git history (up to a certain point), looking for mentioned bugs that are still open: https://github.com/rossburton/ross-tools/blob/master/git-find-bugs No idea if it still works...