repothing
Being built · a working Go prototype
Every repo at a glance. Nothing left unpushed.
With agents working across dozens of repositories, nobody knows what is uncommitted or unpushed. repothing answers it in one command.
- 1 table for every repository
- 0 force pushes to a default branch
- 1 queue of open pull requests
- Dry run until you say execute
Features
The chores that repeat, as commands.
-
Everything unsaved
Branch, unpushed commits and uncommitted files for every repository under a root, in one table.
-
Protected from its agents
No force pushes or deletions on default branches, and changes land as pull requests.
-
One review queue
Every open pull request in one list, ordered by what needs you first.
How it works
Safe to run across everything.
-
1
Report first
Anything that changes something reports what it would do, and acts only with
--execute. -
2
Exit loud
checkexits non-zero when work is at risk, so it can run on a timer and complain. -
3
Say cannot
Where the platform refuses, it says so and why, so an unprotected repository is a finding, not a footnote.
Who built it
Built by Rytter.
I'm Jakob Rytter. I build software and run it, from the server to the screen, and repothing is how I keep track of mine.