I just force push the same commits, so you won't know if it was me or the ai that wrote various parts /s
I actually lead my commit messages with (human) or (agent) now
You could try using a git worktree that never gets pushed
I actually lead my commit messages with (human) or (agent) now
You could try using a git worktree that never gets pushed
I have one client where force push and rebase are not allowed, knots of history are preferred for regulatory compliance, so I'm told. Bisecting is not something I've heard done there before
I like rebasing! It works great for bisecting, reverting (squash messes that up), almost everything. It just doesn't play well with micro commits (which unfortunatelly have become the norm).
The force pushing to the PR branch is mostly a consequence of that rebase choice, in order to not pollute the main branch. Each change in main/master must be meaningful and atomic. Feature branches are other way to achieve this, but lots of steps involved.