On Sat, Sep 12, 2015 at 02:31:11PM -0700, W. Trevor King wrote: > On Sat, Sep 12, 2015 at 11:15:14PM +0200, hasufell wrote: > > Because that is not a valid bug report. Patches must be attached > > to bugzilla. > > Right, thanks. In that case, I think you'll need a hook to push a > new patch whenever the GitHub branch is updated, rebased, etc. That > could make for a lot of Bugzilla spam…
Coincidentally, I was catching up on Git Rev News [1], and the 2015-06-03 post talks about Git itself picking up a GitHub PR → upstream submission tool [2]. The Git Rev News post reproduces the workflow notes from the anouncement on the Git list [3], but the main point is that users trigger submitGit [4,5] manually, to have it push the pull-request upstream (in their case as a series of patch emails, but for us it would be to a Bugzilla patch). There's no mechanism for syncing comments (inline or otherwise) between GitHub an the mailing list, folks just keep discussion on the mailing list [3]. I haven't looked through the Git list to see how this approach is going for them, but it does mean that at least some folks who prefer GitHub PRs for submitting patches will punch an extra button or two to submit the series upstream and use the upstream channel to continue discussion. A similar approach may be an option for us, with a button to push a PR to Bugzilla. The initial button-push would send over a patch and start syncing comments, and subsequent button-pushes would send over revised patches. Cheers, Trevor [1]: http://git.github.io/rev_news/rev_news.html [2]: http://git.github.io/rev_news/2015/06/03/edition-4/ [3]: http://thread.gmane.org/gmane.comp.version-control.git/269699 [3]: https://submitgit.herokuapp.com/ [4]: https://github.com/rtyley/submitgit -- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
signature.asc
Description: OpenPGP digital signature
