Thread

1. dizzard · 1790352178 · focus · HN ↗

   My favorite VCS friendly ticket tracker is <a href="https:&#x2F;&#x2F;github.com&#x2F;wedow&#x2F;ticket" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;wedow&#x2F;ticket

   It&#x27;s human-readable, simple, and easy to work with. Basically there&#x27;s no magic.

   1. lemontheme · 1790369593 · focus · HN ↗

      Yeah, ticket is great! I liked it so much I ended up porting it to Python, which I find easier to read than awk&#x2F;sh, and tweaking the command surface over dozens of iterations of trying to make the design more ‘self-explanatory’ for coding agents. <a href="https:&#x2F;&#x2F;github.com&#x2F;a3lem&#x2F;tiquette" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;a3lem&#x2F;tiquette

      (Excuse the vibe-coded README)

      Anyway, even though I’m using it every day, I’m beginning to doubt the core idea of tracking hundreds of .md files in git. They get in the way of fuzzy file search, and if you keep closed tickets around in an archive directory, they just pile up endlessly.

      Lately I’ve been considering breaking tickets out of VCS entirely or moving them to a dedicated repository just for ticket tracking.

      Git bug looks like it might at least handle getting tickets out of the way

Unofficial Hacker News client; not affiliated with Y Combinator.