Worktrees are conceptually very simple: they allow you to manage multiple working trees in the same repository. In layman’s terms, this means you can check out multiple branches at a time. You may still be subjected to long build times, but you can keep a worktree, and associated IDE window, open and ready for incremental tinkering while you wait for your builds. Each worktree creates a directory with its own copy of the entire project. These directories contain private .git files, which effectively alias to the shared .git directory of the parent tree. Agents love worktrees... and I’ve kinda gone off them. I prefer just having separate copies of the same checkout, like multi/1, multi/2, and multi/3, and spawning agents inside these folders.

Workday has asked a US judge to reject a bid to allow potentially millions of job applicants to pursue discrimination claims against the company as a group over its AI-powered screening software used by hundreds of employers