After a few minutes of playing around: * There does not seem to be any documentation * What are keywords to close a task in a commit. Does it have to be in E

After a few minutes of playing around: * There does not seem to be any documentation * What are keywords to close a task in a commit. Does it have to be in English? Can the words be customized? * Can I import from external projects (i.e. Everyone on github uses something else today and needs to migrate) * Where are issues stored? Are they stored in a git repo? * Can I export? * When you make a label shouldn't it pick a color automatically? * What about when I merge issues from forked projects, when they Close task #12 is that their #12 or my #12? * If I rebase and remove a commit that fixed #12 will the issue be updated? * If you fork someones repo do you get the issues? What about when you pull and rebase? How are they merged? * Can I see if any of my forks have fixed issues? * What branch does the issue tracker look in to see if an issue has been fixed? master? Is it customizable? It looks nice, but after poking at it for a minute I am a bit underwhelmed. It is a nice basic and traditional issue tracker, but at least what is exposed is no where near any of the interesting issue trackers built on top of git that people have been playing around with the past year. Maybe it is all built on git and that will be revealed as time goes on, but not sure. Hopefully it wont stop some of the people who have been playing around with issue trackers built on top of git. Part of the joy of Git is that I am not tied to GitHub. Yes I host my projects there, but when it goes down it doesn't matter because I can still keep working. I was really looking forward to a issue tracker that is built on git that I can store in my project tied into GitHub. But this is till very cool and a good step in the right direction.