Hacker News new | ask | show | jobs
Show HN: Git-issues – Issue tracker that lives in your repo as Markdown (steviee.github.io)
1 points by steviee 46 days ago
Hey, I built git-issues to replace GitHub Issues, because

- my very own (probably flawed) workflow sometimes changes planned features along the way which tends to get source code and feature descriptions out of sync - I wanted Claude Code (or Codex) to be faster when accessing the planned tasks - have everything checked out that's needed for work to be able to work offline (sometimes happens on a boat etc.)

So, in short:

Issues stored as YAML-frontmatter Markdown files in .issues/, version-controlled alongside your code. Zero infrastructure: one Go binary, no server, no database, no accounts.

Built for two workflows: - Human: issues list, issues show, issues board (interactive TUI) - Agent: issues next → issues claim <id> → issues done <id>. Auto-generates .agent.md context for Claude Code and other agents.

Relations (blocks, depends-on, related-to, duplicates) are bidirectionally synced. Every change auto-git add-ed. Issues travel with branches, git bisect shows state at any commit.

go install github.com/steviee/git-issues@latest

What do you think?
1 comments
stephenr 46 days ago
This seems like it's possibly a spiritual successor to BugsEverywhere (which is relatively vcs agnostic).

Is there anything about this that is actually git specific or could it work with eg Mercurial?

link
steviee 46 days ago
Hey, good question. The cli tool itself is more or less just modifying files within the repo so you should be good to go with Mercurial or any other vcs. To smooth things out for AI agents the skill files and descriptions would need to be migrated for the respective vcs of course.
link
stephenr 46 days ago
Fair enough. Any plans to have a "serve" mode to serve up a web issues board?
link
steviee 45 days ago
Actually yes and no. The current implementation is more like a monitor of things going on. I used it to visualize the current state of a project that I let AI agents work on. So the board is read-only, and I think that's mostly fine for now. Porting this read-only view to HTML and put a little http/websocket service in there would be easy on the one hand, but break the TUI setting somewhat. Feel free to create an issue for it, though.
link