Who would have thought that git worktree is the technology of the year 2026?
GitHub Copilot App
51–60 of 83 posts
Re: GitHub Copilot App
#52As a side note, has anyone else noticed that GitHub have leaked what looks like a sequential customer number on their Billing - Usage page? Go here and you’ll be redirected with a query string including a customer parameter. That looks like trouble. https://github.com/settings/billing/usage
Re: GitHub Copilot App
#53Re: GitHub Copilot App
#54Who would have thought that git worktree is the technology of the year 2026?
Re: GitHub Copilot App
#55Who would have thought that git worktree is the technology of the year 2026?
How small are people’s projects if they find worktrees useful? I use them for hobby stuff, but $DAYJOB is a different story because of testing
Re: GitHub Copilot App
#56Now they want to end that collaboration, and turn it into automation. Many C-suite executives right now are smiling bigly. Meanwhile, we're leading the exodus. Turns out, we still want the easiest and prettiest way to participate in the collaborative development of software, and GitHub ain't it!
Re: GitHub Copilot App
#57As a side note, has anyone else noticed that GitHub have leaked what looks like a sequential customer number on their Billing - Usage page? Go here and you’ll be redirected with a query string including a customer parameter. That looks like trouble. https://github.com/settings/billing/usage
That information is public https://api.github.com/users/
Re: GitHub Copilot App
#58Who would have thought that git worktree is the technology of the year 2026?
And the team behind opencode is working on an alternative https://github.com/anomalyco/rift
Re: GitHub Copilot App
#59Re: GitHub Copilot App
#60But!
The reason these tools exist is not because of non-professional developers, but quite the opposite.
A lot more professionals are now working on more projects simultaneously- something that was not practical just a year ago.
Though, while this is nice, considering that all of the action is happening on the same device, I am worried this is going to increase supply chain risks. Before, a developer would work on clearly designated projects for practical reasons. Now, the same developer can work across many projects that are quite different - for example, the marketing site and the backend - and because of an obscure and unimportant component on the marketing site, there can be an impact on backend systems.
I wrote more about this here: https://chatbotkit.com/reflections/everyone-is-a-vip-now