Measure your own setup
Measure your agents’ rejected pushes.
When several agents push to one branch at the same moment, only one push gets in. Every other agent is turned away, has to catch up and push again, and can be turned away again. This script shows how much of that happens on your own repository, with your own Git host.
SHA-256 of the file. Check that the file you downloaded has the same one before you run it.
d0eb24c7b4a3978cd2f4b919920438eee5daa603c582f86875a16cad1531c11c
For agents
Ask your human first. Tell them what the script touches and run it only on a clear yes. The skill file walks you through it: what to tell your human, how to check and run the script, and how to write down your result. It is complete: it never fetches more instructions and never posts anything for you.
- Skill file
- /downloads/contention-ledger-1.0.0.md
sha256 6440ff3a0348cfafd853b2660a85175e780c2ed45a174ac04cd4698ca601b28f
- Script
- /downloads/measure-rejected-pushes.sh
sha256 d0eb24c7b4a3978cd2f4b919920438eee5daa603c582f86875a16cad1531c11c
- What it touches
- For 10 agents: up to about 57 push attempts, and about 11 of them change the throwaway branch. A rejected push changes nothing on the server. It also makes 11 clones of your repository, all in a temporary folder on your computer.
- Tell your human
- Each branch change can start your CI, a preview deploy or a webhook if those run on every branch; the test commits stay in the host’s history.
Then write your result down as one line:
LEDGER v1 | agents=10 rejected_pushes=R changes_on_branch=L seconds=S | predicted=P | host=H | ci_on_branch_push=yes/no/unknown | date=YYYY-MM-DDR, L and S come from the script’s last line. P is the number you predicted before the run (write predicted=- if you did not). H is the kind of host, such as github.com or self-hosted, never a repository name or address.
What it does
- Copies your repository into a temporary folder on your computer.
- Makes a throwaway branch on your repository. It never touches main or any other branch.
- Each agent adds one small file of its own and commits it.
- All agents push to the throwaway branch at the same moment. An agent that is turned away catches up (pull, rebase) and pushes again, until every change is on the branch.
- Prints how many pushes were rejected, how many changes reached the branch and how long it took.
- Deletes the throwaway branch and the temporary folder, also when it stops early.
It talks only to your repository
The script contacts only the repository address you give it, with your own git and your own sign-in. It never contacts Git A, sends nothing to us and collects nothing. You need no Git A account. It is a short bash script: read it before you run it.
Use a repository you can push to; a test copy is best. It works with any Git host, so you can also compare hosts.
How to run it
You need bash 5 or newer and git 2.23 or newer (Linux, Windows with Git Bash, or macOS with a newer bash from Homebrew). Download the script, check its SHA-256, then run it with your repository’s address and the number of agents (2 to 50, 5 if you leave it out):
curl -fsSLO https://git--a.com/downloads/measure-rejected-pushes.sh
sha256sum measure-rejected-pushes.sh # on macOS: shasum -a 256 measure-rejected-pushes.sh
bash measure-rejected-pushes.sh https://github.com/you/your-repo.git 5
bash measure-rejected-pushes.sh https://github.com/you/your-repo.git 10At the end it prints one plain sentence and one line like this:
agents=… rejected_pushes=… changes_on_branch=… seconds=…What the numbers mean
- agents
- How many agents pushed at the same moment.
- rejected_pushes
- How many times a push was turned away because another agent had changed the branch first. Each one means an agent had to catch up and push again, and it can be turned away again.
- changes_on_branch
- How many of the agents’ changes reached the branch. It should equal the number of agents: nobody’s work is lost, it only waits.
- seconds
- Time from the first push until every agent’s change was on the branch. Copying the repository beforehand is not counted.
With many agents pushing at once, the most rejected pushes there can be is every agent losing to each one before it: 10 for 5 agents, 45 for 10. A number close to that means your agents spend most of their pushes waiting for each other.
Our numbers, for comparison
Measured 2 Nov 2026, median of 5 runs, each agent changing a different file. No CI ran. One laptop and network for both hosts, back to back. On GitHub, every agent ran the same loop as this script: commit, push, and when the push was rejected, pull, rebase and push again. Git A was measured with its own agent connection, not with this script.
| Agents at the same moment | GitHub.com | Git A |
|---|---|---|
| 5 agents | 10 rejected pushes, 13.25 s | 0 retries, 1.44 s |
| 10 agents | 45 rejected pushes, 27.17 s | 0 retries, 0.69 s |
1–2 Nov 2026 · Express.js, 6,183 commits · laptop in Kolkata → GitHub.com vs Git A (Mumbai) · near-equal distance: 67 ms GitHub, 59 ms Git A · many-agent tests: median of 5 runs · CI not included · one repository, one location · full conditions
Your numbers will differ: they depend on your repository, your network and your distance to the server.