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