Live data from Hacker News

Show HN: Watson – inline issue manager with GitHub support

goosecode.com

1–10 of 41 posts

Re: Show HN: Watson – inline issue manager with GitHub support

#5
post #4

Screenshots make this thing really interesting. Need to support more languages than just Ruby and Perl!

Thanks! The app is written in both Ruby and Perl but it currently has support for parsing C / C++, Java, C#, Bash, Ruby, Perl, and Python files

Re: Show HN: Watson – inline issue manager with GitHub support

#7
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 ?

Re: Show HN: Watson – inline issue manager with GitHub support

#9
Great idea! I've wanted something like this for a while, but never quite realised it.

What languages does it support? From the look of the front pages, C-based languages (C/C++/Obj-C) are ok.

Have you thought about offering this as a service? You could probably hook into Github and sync issues on commit using the same API that Jenkins uses.

Re: Show HN: Watson – inline issue manager with GitHub support

#10
post #7

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…

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.
Post reply on HN