I will keep my PRs that are not yet ready to be merged, even if from a implementation POV its "done". The other option is to update the PR title or add a header in the top of the PR body to flag that it's not to be merged. I wasn't done with verifying my changes in the browser, but the PR got merged. I need to signal to the entity (flesh-and-bones colleague or AI agent) that it's not to be merged yet more strongly. I'm assuming legit mistake by the entity who merged the PR, maybe they didn't read the PR body or the comment activity on the PR activity thread. I lost time that I could have used to work on a more impactful feature, due to managing multiple git worktrees and branches, since the merge pruned the feature branch from remote.

Answer this

This is Proof — engineers thinking in the open.

You get read for how you actually reason — not a résumé keyword. Free to join.