Github-Todos – Git hook to convert your TODOs into Github issues
1–10 of 20 posts
Re: Github-Todos – Git hook to convert your TODOs into Github issues
#2neat
Re: Github-Todos – Git hook to convert your TODOs into Github issues
#3If this works as advertised, this is awesome. I've always used TODOs in my projects, and haven't always used github due to employer constraints. Now I won't have to put so much effort into keeping track of open tasks.
Re: Github-Todos – Git hook to convert your TODOs into Github issues
#4If this works as advertised, this is awesome. I've always used TODOs in my projects, and haven't always used github due to employer constraints. Now I won't have to put so much effort into keeping track of open tasks.
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 never occur).
Give it a try on a sample repository, always needing more testers !
Re: Github-Todos – Git hook to convert your TODOs into Github issues
#5Excellent! At the moment, I dump all my TODOs in a section in my readme, but if the relate to specific lines of code, it's a mess trying to trace what the TODOs were referencing when I try to go back and work on them many months later.
Once question, once a TODO is removed from the repository, is the issue also automatically closed? Or vice-versa? Would be cool if the two were coupled, so that there aren't dangling TODOs left in the repository once the issue has been addressed in some fashion.
Re: Github-Todos – Git hook to convert your TODOs into Github issues
#6Excellent! At the moment, I dump all my TODOs in a section in my readme, but if the relate to specific lines of code, it's a mess trying to trace what the TODOs were referencing when I try to go back and work on them many months later. Once question, once a TODO is removed from the repository, is the issue also automatically closed? Or vice-versa? Would be cool if the two were coupled, so that there aren't dangling T…
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 a removal, can be tougher) — maybe a TODO previously related to this issue will have to be modified instead of deleted, how should it handle it?
When TODO is removed :
— should I close issue directly or check in the whole codebase if it still exists somewhere and keep it open?
Many questions arise and I still found no harmless answers :(
But it definitely should help you track it both ways, with a command "stat" for example that would report you any actions you should achieve, and even interactively do it for you. But I don't think it will happen in hook itself yet.
I want all ideas available here ;) should create an issue for open discussion.
Re: Github-Todos – Git hook to convert your TODOs into Github issues
#7Great idea! Integrating with Githooks is super convenient.
This reminds me of watson (https://github.com/nhmood/watson-ruby) which manages TODOs pretty well (with GH support) but doesn't generate the hooks for you unfortunately.
Re: Github-Todos – Git hook to convert your TODOs into Github issues
#8Excellent! At the moment, I dump all my TODOs in a section in my readme, but if the relate to specific lines of code, it's a mess trying to trace what the TODOs were referencing when I try to go back and work on them many months later. Once question, once a TODO is removed from the repository, is the issue also automatically closed? Or vice-versa? Would be cool if the two were coupled, so that there aren't dangling T…
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 a removal, can be tougher) — maybe a TODO previously related to this issue will have to be modified instead of deleted, how should it handle it? When TODO is removed : — should I close issue…
I'm just throwing out an idea here; I don't know if it's possible.
Put some sort of tag in the todo comment to represent a change. e.g. // TODO: Fix this issue #complete
At commit time, the hook will see the tag changed, reference the commit in the issue, and then auto-close it.
Re: Github-Todos – Git hook to convert your TODOs into Github issues
#9This looks pretty promising. It would be awesome if we could easily change the providers. (gitlab, bitbucket, trello etc)
Re: Github-Todos – Git hook to convert your TODOs into Github issues
#10This looks pretty promising. It would be awesome if we could easily change the providers. (gitlab, bitbucket, trello etc)
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.