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
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
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 <(510)%20486-5709> Email : [email protected] Fax : 510-486-5909 <(510)%20486-5909> Web : CCI.LBL.gov
On Fri, Dec 9, 2016 at 6:23 AM, Luc Bourhis
wrote: Hi Graeme,
Does anyone have an objection to opening up the issue tracker on […]
Your thoughts?
+1
Best wishes,
Luc
_______________________________________________ cctbxbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/cctbxbb
_______________________________________________ cctbxbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/cctbxbb
_______________________________________________ cctbxbb mailing list [email protected] http://phenix-online.org/mailman/listinfo/cctbxbb