I would love to watch a day of programming by someone as prolific as Simon to see what other things he does to maintain speed and keep churning out code!
I would love to watch a day of programming by someone as prolific as Simon to see what other things he does to maintain speed and keep churning out code!
Unless you care about project portability. In which case, GH issues are obviously the wrong, locked-in place to put things.
Not that there is an obvious solution to this problem. There are a few tools trying to fix this, but they're still a bit awkward. I wish Git added a somewhat-native/idiomatic way to deal with it.
The counterpoint to this is that GitHub has been around for a long time and I don't think all of these free features are going anywhere. Even beyond that, there's an API you can use to get your data out and lots of tools build on that API.
https://github.com/MichaelMure/git-bug came up here recently and that looks pretty good, though I haven't tried it. I suspect the usability of a lot of these tools will lag behind GitHub Issues/Projects.
It's still an external system you don't control the fate of, run by an private company, fundamentally unaccountable, and a massive single point of failure. For some people, this is not a good thing. It's a bit like using GMail vs an actual mail client.
I reckon git has already all the low-level features it needs to make this work, it just needs a bit of porcelain on top.
> How do we link to these issues
The same way we link to commits today? As in, we don't - not in the tool itself. The critical part is that such managers will want a nice web interface, not a command line tool. That's the porcelain I mentioned.