3 ms·

I was trying to find an issue management system for doing “the perfect commit” and tried loads without thinking of GitHub issues, which is obviously the correct

I was trying to find an issue management system for doing “the perfect commit” and tried loads without thinking of GitHub issues, which is obviously the correct place to put things. Exciting to hear about GitHub projects too which sounds fantastic! 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!

toyg 4y ago
> GitHub issues, which is obviously the correct place to put things 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.
- andy_ppp 4y ago
  Yes people were looking to use git notes for this but it currently looks hacky - maybe a .issues folder and some cli tooling could help here but I guess getting consecutive IDs could be a pain/cause conflicts. Sub-issues might also be difficult.
  - toyg 4y ago
    Do we really need consecutive numbers? Any short letter-number combo would work fine, which could be done with simple hashes. 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.
    - andy_ppp 4y ago
      I think project managers might freak out at `PROJ-3eff1a` but maybe you work with more technical managers than I do. How do we link to these issues, I suppose you could build a read only ui for them or maybe each issue is a folder with a README.md in it? It’s a lot of work to make something useful at work.
      - toyg 4y ago
        Surely for a manager in tech, it wouldn't be too difficult to use "3eff1a" where they used "#2345". > 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.
- dangoor 4y ago
  (Disclaimer: I work for GitHub, but not on issues, and I've only been here 6 months) 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 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.
  - toyg 4y ago
    > GitHub has been around for a long time and I don't think all of these free features are going anywhere 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.

toyg 4y ago

> GitHub issues, which is obviously the correct place to put things 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.

andy_ppp 4y ago
Yes people were looking to use git notes for this but it currently looks hacky - maybe a .issues folder and some cli tooling could help here but I guess getting consecutive IDs could be a pain/cause conflicts. Sub-issues might also be difficult.
- toyg 4y ago
  Do we really need consecutive numbers? Any short letter-number combo would work fine, which could be done with simple hashes. 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.
  - andy_ppp 4y ago
    I think project managers might freak out at `PROJ-3eff1a` but maybe you work with more technical managers than I do. How do we link to these issues, I suppose you could build a read only ui for them or maybe each issue is a folder with a README.md in it? It’s a lot of work to make something useful at work.
    - toyg 4y ago
      Surely for a manager in tech, it wouldn't be too difficult to use "3eff1a" where they used "#2345". > 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.
dangoor 4y ago
(Disclaimer: I work for GitHub, but not on issues, and I've only been here 6 months) 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 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.
- toyg 4y ago
  > GitHub has been around for a long time and I don't think all of these free features are going anywhere 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.