Git-issues – Issue tracker that lives in your repo as Markdown
Issues as Markdown files in your repo means they finally travel with your branches.
Repository based Issue Tracker (think Github Issues) for AI Agents
Issues as versioned Markdown files means you can branch, revert, and diff task history with git.
Solo developers and AI agent workflows
gitit · repo-issue-trackers
I built git-issues to be used as a replacement for my Github Issues based workflow where I direct my coding agent to put up tasks and context besides the README.md.
This works as long as the Github Issues and what you're actually developing is in sync. However you can't just branch out, change the plan and explore something that easily with non-versioned Tasks. Also you can't revert to a certain composition of tasks just like that.
All this changes when your tasks are part of the repo and commit-history.
It's all self-contained.
Hope you find it useful.
Best, Steviee
Issues as Markdown files in your repo means they finally travel with your branches.
Git-native issues AI agents can manage, but GitHub Issues + MCP already solve this better.
Git-based memory you own beats vendor databases — review facts in PRs.
Git-native issues as markdown files, but GitHub Issues, Gitea, and Fossil already solve this.
Issues as Git commits, finally solving Linus's 2007 proposal after 17 years.
Git as the agent standard — version prompts like code before LangChain locks you in.