- From: Gregg Kellogg <gregg@kellogg-assoc.com>
- Date: Wed, 9 Nov 2011 15:20:57 -0500
- To: Karl Dubost <karld@opera.com>
- CC: Stéphane Corlosquet <scorlosquet@gmail.com>, Robin Berjon <robin@berjon.com>, "spec-prod@w3.org Prod" <spec-prod@w3.org>, Manu Sporny <msporny@digitalbazaar.com>
On Nov 9, 2011, at 11:29 AM, Karl Dubost wrote: > Is there a way in github to associate an ISSUE number with a commit? > There is no action item too. How did people replace that. See Github flavored markdown: http://github.github.com/github-flavored-markdown/ You can mark commits and issues within the issue tracker. According to http://stackoverflow.com/questions/1687262/link-to-github-issue-number-with-commit-message, you can also do this in commit messages. So, you could do a commit with "Closes #1" and it would link to that issue and close the issue. Typically, I usually do the commit and then close the issue. In which case, I really should mark add the commit ID to the issue when closing it. Of course, this can be done after the fact. For action items, we usually note them in the IRC log and then someone manually creates the issue. Better workflow would be to auto-detect ACTION to raise an issue, and detect referenced issues when processing the IRC and add comments to the issue. This could also implement the "Closes #1" type behavior when issues are RESOLVED in IRC. Gregg > slightly off-topic > > Le 9 nov. 2011 à 11:33, Stéphane Corlosquet a écrit : >> We decided to move them all to the W3 tracker and only use the W3 tracker from then onwards (we only had 8 at the time so the manual process wasn't too hard). > > I have seen that discussion a few times already. > We are always talking about user data portability and "its social graph". :p > And we seem to be unable to deal with distributed issues system. I wish we > had a shared protocol/format/issues for these. > > -- > Karl Dubost - http://dev.opera.com/ > Developer Relations & Tools, Opera Software >
Received on Wednesday, 9 November 2011 20:21:50 UTC