Two Logs

Two Logs

One builder keeps two commit logs. The public one is written to someone who has never shown up, and it shows.

Two repos. One builder.

The private one has a commit log that reads: wip. fix. fix again. actually fix. Nothing in it explains anything. Nothing has to.

The public one reads differently. Handle empty config on first run. Drop the retry that hid the timeout. Full sentences, from the same hands, often the same night.

Neither has had a visitor.

The difference is not an audience. It is an address. The public repo is written to someone. A person who might open it some afternoon, knowing nothing, unable to ask.

That reader has never arrived. They still get a vote.

They are why the API key never touched a commit. Why the function got a name instead of a letter. Why the message says what changed and what it was hiding. Why the test that passed on one machine got fixed instead of skipped.

A team gets this from review. Someone reads the diff tomorrow, so the diff gets written for them. Solo, there is no tomorrow's reviewer. A public repo supplies an imaginary one, and the imaginary one is strict.

The same reader asks for other things.

A history squashed until it shows no wrong turns. A badge row above a project that does not build yet. A roadmap in a README with no install step. The half-working branch kept on the laptop for a week, so the first push looks like the first try.

One reader. Two kinds of work.

Some of it turns up in the private repo too, on the good days. The clear name. The message that says why.

Some of it never does. Nobody adds a badge row to a repo no one can open.

A public repo has a reader long before it has a visitor.
The private log is what gets written without one.