Hi Nigel, all
That could be harder but not beyond our capabilities I expect
However the response seems to be a resounding go for it, so I’m sure the issue tracker will be activated RSN
Best wishes Graeme
From: [email protected] [mailto:[email protected]]
On Behalf Of Nigel Moriarty
Sent: 09 December 2016 15:43
To: cctbx mailing list
Subject: Re: [cctbxbb] issue tracker on https://github.com/cctbx/cctbx_project
One feature that would be cool is to set a (say) weekly email to remind developers of the issues assigned to them. In my other collabs, there is a complaints that the issues are not being noticed...
Cheers
Nigel
---
Nigel W. Moriarty
Building 33R0349, Molecular Biophysics and Integrated Bioimaging
Lawrence Berkeley National Laboratory
Berkeley, CA 94720-8235
Phone : 510-486-5709 Email : [email protected]
Fax : 510-486-5909 Web : CCI.LBL.gov
On Fri, Dec 9, 2016 at 7:40 AM, Aaron Brewster <[email protected]> wrote:
Also +1. I like how it's possible to reference issues in commits by using #, which then show up as links in the commit emails and website history. One can cite issue numbers, or even interact with them. For example, if your commit includes
the phrase "closes #42" or "fixes #42", then issue 42 will be closed when you push your commit. It's Nifty.
-Aaron
On Fri, Dec 9, 2016 at 7:29 AM, Nigel Moriarty <[email protected]> wrote:
We at Phenix would like to see how the issue/bug tracker works as it's an important feature we'd like to use when we migrate our other repos to GitHub.
Cheers
Nigel
---
Nigel W. Moriarty
Building 33R0349, Molecular Biophysics and Integrated Bioimaging
Lawrence Berkeley National Laboratory
Berkeley, CA 94720-8235
Phone : 510-486-5709 Email :
[email protected]
Fax : 510-486-5909 Web :
CCI.LBL.gov
On Fri, Dec 9, 2016 at 6:23 AM, Luc Bourhis <[email protected]> wrote: