naholyr

10 ms·

1.
by naholyr 12y ago
Ah ah nope, and that arised fast (issue #4) ;) But definitely, if you find it useless, then it certainly is for you! I was just telling why others could find it useful :)
2.
by naholyr 12y ago
It's all about not forgetting to create the issue: you just put your // TODO and not go out of your editor. An IDE plugin could do the trick nicely too (create an issue by right-clicking on a TODO for example). But a git hook
3.
by naholyr 12y ago
Hope it will do the job :) still in active development so… https://github.com/naholyr/github-todos/issues ;)
4.
by naholyr 12y ago
That's more the direction I think about yes
5.
by naholyr 12y ago
Jira should quickly be on its way, in the meantime I'll make everything needed to make the operation of adding a new issue manager a very easy task.
6.
by naholyr 12y ago
This coupling is not ready yet, I still have to find a satisfying workflow. When issue is closed : — it detects TODOs anywhere, not necessarily in comments, it could destroy some code (same for 'inject-issue' but here it would be
7.
by naholyr 12y ago
Hi I'm the author :) Note that it can open or comment issues (matching based on TODO's text == issue's title), but it does not yet closes them, because I couldn't find a satisfying workflow yet (which means it may neve
8.
by naholyr 12y ago
In this situation, "foo" or "bar" or both should not depend on baz, but have it as a peer dependency. There is nothing broken, just a very specific case not so easily identifiable, but very easily fixable.