potiuk commented on PR #73836: URL: https://github.com/apache/airflow/pull/73836#issuecomment-5872475449
> I don't see anything related to worktree deletion in https://git-scm.com/docs/githooks. The CLI does nothing automatic to detect the current worktree. I could have three projects on the same main checkout, and that's by design. The use of workflows is that they are often created and deleted on demand - `claude -w` for one will create one, and when you complete working on it it will ask you whether to remove it. This will lead to many un-deleted docker-composes, because during agentic sesion/testing the LLM might simply start breeze to run tests - and used might not even be awary that they should clean-up. Breeze has been designed to handle just "several - but static set of projects" simply. We do it in Magpie, but indeed those hooks were Claude hooks. I think the easiest way is: 1) record (in ~/.breeze) which worktrees (folders) breeze project runs on associate docker project with it 2) at the start of any breeze command check if the folders still exist - and `docker compose --project PROJECT down --volumes --remove-orphans` for such project. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
