This is awesome. We the developers love to put those little comments in code for issues/to-dos and syncing it with Github is solid. looks like someone needs to fork it for Python ?
One question though. When an issue is resolved, would that actually go back to the source file and delete that inline comment OR would it add the text "resolved" etc. In both cases though, would we not need a new commit to that source file ? Or does it leave the inline comment in its original state ?
It currently leaves the inline comment in its original state. It didn't seem like a good idea to have an automated tool touch the code itself, watson leaves it up to the developer to remove the comment.
The "resolved" tag only appears in the report when the issue is resolved on GitHub or Bitbucket to notify a user that they can either remove it or ignore working on that issue.
What about encouraging use/automated installation of local git hooks, ie. run watson locally after a successful push. I've just begun looking at git hooks but this seems like exactly the sort of thing they were intended for
This is cool. I built something similar to this in Node. You start the tool and it monitors all files in your project folder for changes. Every time you save, it outputs a JSON object of all your tokened comments. The idea was to be able to plug it into another service, like a custom todo list app, or something like this. I haven't quite finished it, but maybe I'll clean it up a bit and push it to github this weekend.
Agree with the general preface of not interrupting your flow with issue tracking. I've been using ghi (command line GitHub Issues)[1] and couldn't be happier.
Super nice. Combining this with most support for updating issues via commit messages this makes it stupid easy to almost never leave the code. The only thing you likely can't easily do is deal with issue comments but that would be killer too. Never having to use the githib UI would be the ultimate workflow boon. I'm never a fan of needing to access websites and remember their UI as it feels disjointed from my typical working experience.
Should be pretty simple to get it working with PHP right? Also, any plans for GitLab issues support? If not, that might be fun to hack on this weekend...
I helped to test this and have been using it since.
it is much less disruptive to work flow to just add comments in one place rather than add comments and have to go through github's ui for work items, bugs, etc.
I love it. Good example of enriching the development environment without any kind of special files, databases, etc. Would be great to port it other issue trackers.
One question though. When an issue is resolved, would that actually go back to the source file and delete that inline comment OR would it add the text "resolved" etc. In both cases though, would we not need a new commit to that source file ? Or does it leave the inline comment in its original state ?