... FinderGit 0.56.12 is a fixes release Got a branch and a tag with the same name? FinderGit used to list the branch

... question about logging what it actually ran is still open for me. I don't have a good answer there. Comment from Giovambattista Fazioli(@gfazioli): @wwenioaguiar   @neelagiri_chettiyar  I agree - at first, ages ago , I used the branch approach - but with worktrees + a parent folder + agents, everything seems to run smoothly and you can do 4 or 5 things at once on the same project without things getting messsy Comment from Giovambattista Fazioli(@gfazioli): @neelagiri_chettiyar   @wwenioaguiar ... ... neelagiri_chettiyar  agreed, the tmux + ssh setup is a solid way to keep a single source of truth And there are a couple more tricks that help a lot once you're in "agents" mode: "/fork" lets you branch

... read what an unreachable database would have produced. On the invoice form, a validation error made of an SQLSTATE line, on a form the user cannot fix. On checkout, a message saying the payment had permanently failed, from the branch meant for refusals, while the branch

... empty state needs handling. Errors need messages. Settings need a place to live. None of these feel optional in the moment, but a week later I look up and I've spent most of my time on the branches instead of the trunk. So my question is about where you draw the line while you're still in the middle of building. How complete does the core feature need to be before you call it done ... ... ugly errors, no settings and fix it only if users complain? Or is there a minimum level of finish below which people won't even try it? And more practically: how do you tell the difference between a side branch

... none of it was a config mistake. Our generator page had a link meaning save this to my account, and it was computed from whether you were signed in, so a signed-in visitor skipped the signup step. One branch, on the highest traffic page we have, and it gives the page two bodies. A page with two bodies cannot be handed to a shared cache, so the framework did the correct thing and marked it uncacheable, silently, for months ... ... forwards a visitor who already has one. The page went from two bodies to one, and became cacheable as a side effect. Nine pages moved. One deliberately did not, and that is the more interesting half. Our pricing page branches

... just me or other devs face it too. I use Jira and GitHub MCPs inside claude code to fetch my tickets and complete them as autonomously as possible. But it always keeps messing up finding the correct repos, branching properly or delivering a PR without CI failing. And I end up repeating instructions and copy-pasting CI errors and asking to fix it. I tracked this and I spent on avg 75mins a day repeating context and instructions. Anyone also ... ... three sessions later. Making it a numbered gate the agent has to clear before the write step is what actually stopped it. Worth splitting your 75 minutes into which kind you're repeating. If it's facts, repo names, branch

... scraper node was supposed to rotate its address after being blocked too often. It had rotated zero times in twelve hours. The block counter was fed in the general error path, but a captcha was caught by an earlier branch that returned before reaching it. So the one failure the entire mechanism existed for was the one failure it could not see. The node called itself healthy the whole time it was being turned away. Three. My public status page ... ... which changes on every restart, so the status page counted phantom machines for weeks. Twelve hours passed with zero rotations because the block counter was fed on a general error path while the real failure returned in an earlier branch

... solved the "explaining a system clearly" problem but a GDD full of well-connected notes still left a gap before anything became a testable prototype. This release closes that gap. A designer can now sketch a quest, write the branching dialogue for the NPC who gives it, block out the level layout where it takes place, and rough in the UI that displays it to the player, all inside one connected canvas, without switching between four different tools that ... ... scattered notes to something a team can actually walk through and test, faster than assembling the same thing across a notebook, a spreadsheet, and a whiteboard tool. What's Actually New in 1.0 Dialogue creation. You can now plan branching

... story. A rule the agent can read is a rule the agent can ignore. So the commit block has to live below the agent, deny git commit at the permission layer, or point it at a scratch branch and keep main untouched, so "don't commit" isn't a thing it can choose to forget. Curious though, when it committed against your instructions, did it think it was helping? That's the part that unsettles me more than plain bugs ... ... disobedience, it's the agent being confidently sure the commit was the right call. Comment from Aadil Ghani(@aadilghani): @roopesh_donde   Honestly, getting burned once is how basically everyone learns to branch

... doorbell. It rings the same whether it's a package or a fire. That's basically the gap Pushary fills, same hook idea you've already wired, but the event carries a real handoff (done vs blocked vs