#worktree — Public Fediverse posts

Did some tidying of my repos on @worktree (https://worktree.ca/taffer?tab=repositories) and @Codeberg (https://codeberg.org/Taffer?tab=repositories) this morning. Now all of the Codeberg repos are properly mirrored from Worktree via push-on-commit so I'm not spamming Codeberg. #worktree #codeberg

Did some tidying of my repos on @worktree (https://worktree.ca/taffer?tab=repositories) and @Codeberg (https://codeberg.org/Taffer?tab=repositories) this morning. Now all of the Codeberg repos are properly mirrored from Worktree via push-on-commit so I'm not spamming Codeberg. #worktree #codeberg

Git worktrees question. (Which, as usual, I think I answered while trying to ask a clear question...)

I just learned about worktrees and they seem great. So I have my repo, all the files are checked out, and I do `git worktree add` to add a "foo" worktree.

Now, in my base repo, I have a directory "foo".

Git says it's an untracked file. Which...okay, it is, but shouldn't it be smart enough to see that the directory is a worktree and it makes no sense to say it's untracked?

Another question: I start my IDE in the base repo, and it sees all the worktrees as just more directories and shows all the code in there. This is confusing -- in fact, I just made a code change in a file and was surprised that "git status" in my base repo didn't show it -- because I did the edit in one of the worktrees. But my IDE (IntelliJ, FWIW) was started in the base repo.

Is there any kind of `.ideignore`, analogous to `.gitignore`? Something where I can say "hey $IDE, please ignore all these files"?

My guess for an answer is: "don't do that, that's silly, because...it causes exactly the problems you just described. Putting a git repo inside itself is silly. Use a separate directory elsewhere."

#git #worktree

Git worktrees question. (Which, as usual, I think I answered while trying to ask a clear question...)

I just learned about worktrees and they seem great. So I have my repo, all the files are checked out, and I do `git worktree add` to add a "foo" worktree.

Now, in my base repo, I have a directory "foo".

Git says it's an untracked file. Which...okay, it is, but shouldn't it be smart enough to see that the directory is a worktree and it makes no sense to say it's untracked?

Another question: I start my IDE in the base repo, and it sees all the worktrees as just more directories and shows all the code in there. This is confusing -- in fact, I just made a code change in a file and was surprised that "git status" in my base repo didn't show it -- because I did the edit in one of the worktrees. But my IDE (IntelliJ, FWIW) was started in the base repo.

Is there any kind of `.ideignore`, analogous to `.gitignore`? Something where I can say "hey $IDE, please ignore all these files"?

My guess for an answer is: "don't do that, that's silly, because...it causes exactly the problems you just described. Putting a git repo inside itself is silly. Use a separate directory elsewhere."

#git #worktree

Claude Code の「待ち」がもったいないので、worktree で並列開発してみた
https://qiita.com/yasuto_88/items/15f57336baed3ef64a10?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #Git #AI #worktree #AIエージェント #ClaudeCode

Hot take: AI coding tools will do more to popularize Git worktrees than a decade of documentation ever did.

#AI #LLM #Git #Worktree #GitWorktree #SoftwareDev #SoftwareDevelopment #Claude #ClaudeCode #Copilot #GitHubCopilot

Hot take: AI coding tools will do more to popularize Git worktrees than a decade of documentation ever did.

#AI #LLM #Git #Worktree #GitWorktree #SoftwareDev #SoftwareDevelopment #Claude #ClaudeCode #Copilot #GitHubCopilot

https://medium.com/@natescode/multitask-like-a-pro-with-git-worktree-151650bdfd11 - A super simple tutorial on #Git #worktree: `git worktree add .worktrees/hello-world/bug/fix-bar bug/fix-bar`

https://medium.com/@natescode/multitask-like-a-pro-with-git-worktree-151650bdfd11 - A super simple tutorial on #Git #worktree: `git worktree add .worktrees/hello-world/bug/fix-bar bug/fix-bar`

Git worktree posouvá práci s větvemi na úplně jinou úroveň – místo neustálého přepínání a stashování nabízí paralelní pracovní prostředí nad jedním repozitářem. V kombinaci s nástroji jako Claude Code navíc otevírá dveře k běhu více AI agentů současně, každý izolovaně ve své větvi, bez kolizí a zbytečné režie.

@TeaDrivenDev Okay, I'm done with worktrees. They're just not fully baked in terms of tooling. #git #worktree

@TeaDrivenDev Okay, I'm done with worktrees. They're just not fully baked in terms of tooling. #git #worktree

Seems like I need to wrap my head around #worktree's and #ddev 🤔 https://www.fldrupal.camp/session/use-git-worktree-ddev-run-multiple-versions-same-site

Seems like I need to wrap my head around #worktree's and #ddev 🤔 https://www.fldrupal.camp/session/use-git-worktree-ddev-run-multiple-versions-same-site

git worktreeを使用した開発の個人的詰まりポイント
https://qiita.com/I635230/items/c23d334cc5adb9e8efd0?utm_campaign=popular_items&utm_medium=feed&utm_source=popular_items

#qiita #Git #worktree

Прощай Cursor

Claude добавил новую фичу в десктопной версии. А именно, в интерфейсе появилась третья закладка - Code. Главное нововведение - это возможность подключать код проекта прямо в чат и работать с ним без копипаста.

https://habr.com/ru/articles/1003310/

#claude_code #Cursor #claude_opus_46 #claude_sonnet_46 #Slash_commands #worktree #CLAUDEmd_файл

Are you working with git worktrees? I made small utility to help me working with them https://github.com/abtris/worktree-util maybe will be useful for someone else too. #git #worktree #tui

Are you working with git worktrees? I made small utility to help me working with them https://github.com/abtris/worktree-util maybe will be useful for someone else too. #git #worktree #tui

I use #Git. A feature of Git I leverage heavily is #Worktree. I usually have at least four around at a time. For small tasks, sure, a simple branch and then switch back, but bigger things: a worktree.

Making a worktree is actually annoying for me: not just the upfront decisions about branches and start points and where to put the new directory (and also immediately `cd`ing there: but getting all the #submodules (submodules suck by the way), hooking up `.envrc` if you use #Direnv (and you should be), which should then set up your virtual environment and path and stuff. Clone isn’t quite as bad but has some of the same problems.

I do this so often, I wrote a script. It might be useful to others with this workflow. It’s opinionated, and therefore I could really use some feedback! What did I do right? What did I do that’s only right for me? What is totally missing?

The script is stand-alone, though you do need #UV. (You don’t even need Python! `uv` will transparently get you everything!) Just download this one Python file, and get it on your `$PATH`. If you want the additional `cd` behavior, then add the shell function, too as described in the `README`. Everything is tested. The tests are right there, too.

https://github.com/wolf/dotfiles/blob/main/git/dot-config/git/bin/make-worktree.py

The `README.md` is right next to it.

I **do** see one thing I’m missing: I need to provide a way to automatically copy in your custom stuff. I’ll add that today.

Вы больше не новичок в Git. Повышаем квалификацию с помощью 7 команд

Каждому разработчику когда-нибудь приходилось срочно переключаться между ветками, восстанавливать потерянный коммит или аккуратно вырезать одно исправление. Это можно делать примитивно с помощью базовых команд Git, но настоящий профессионал отличается от любителя тем, что применяет самые оптимальные решения, тем самым экономит время и нервы. О таких решениях поговорим далее в статье.

https://habr.com/ru/companies/ruvds/articles/978320/

#git #github #git_команды #гит #фичи #worktree #tig #алиас #git_rebase #ruvds_статьи

Worktree is the wholly Canadian (Montreal) GitHub replacement. Started there a couple of weeks ago.

The site is built and run by BlackieOps owned by Alex Black. I found it a tad awkward blackieops listed GitHub as the home to all their repos, not worktree.

#buyCanadian #elbowsUp #worktree

Worktree is the wholly Canadian (Montreal) GitHub replacement. Started there a couple of weeks ago.

The site is built and run by BlackieOps owned by Alex Black. I found it a tad awkward blackieops listed GitHub as the home to all their repos, not worktree.

#buyCanadian #elbowsUp #worktree

I was busy with deploying a website this week, but guess what, more articles for y'all!

https://bojidar-bg.dev/blog/2025-10-24-bare-git-cicd/

This one is about everything I learned about using a bare git repository with hooks to automate deployment. ✨ Git hooks are awesome!!

#100DaysToOffload #git #worktree

I was busy with deploying a website this week, but guess what, more articles for y'all!

https://bojidar-bg.dev/blog/2025-10-24-bare-git-cicd/

This one is about everything I learned about using a bare git repository with hooks to automate deployment. ✨ Git hooks are awesome!!

#100DaysToOffload #git #worktree

Just recently started using #git's #worktree feature, and now I wish I did this years ago. Being able to not just view but do actual work in more than one branch in parallel — without having to stash/commit/checkout all the time.. absolutely amazing. I'm still new with this, so could be there are some things (good or bad) I have yet to discover... but at least currently this feels like the most underrated feature of git that I'm aware of.

https://git-scm.com/docs/git-worktree

Just recently started using #git's #worktree feature, and now I wish I did this years ago. Being able to not just view but do actual work in more than one branch in parallel — without having to stash/commit/checkout all the time.. absolutely amazing. I'm still new with this, so could be there are some things (good or bad) I have yet to discover... but at least currently this feels like the most underrated feature of git that I'm aware of.

https://git-scm.com/docs/git-worktree

How to use git worktree effectively with Python projects https://www.andreagrandi.it/posts/how-to-use-git-worktree-effectively-with-python-projects/

#git #development #worktree #Python

How to use git worktree effectively with Python projects https://www.andreagrandi.it/posts/how-to-use-git-worktree-effectively-with-python-projects/

#git #development #worktree #Python

I spent some time today setting up an external diff driver for #meld in a #git #worktree. Then I wrote up a #orgmode document and published it as a #blog post at https://davemq.github.io/2025/07/11/git-worktree-diff-meld.html

I spent some time today setting up an external diff driver for #meld in a #git #worktree. Then I wrote up a #orgmode document and published it as a #blog post at https://davemq.github.io/2025/07/11/git-worktree-diff-meld.html

@treyhunner @webology Likewise! Worktrees are useful for projects like CPython where we have `main`, `3.14`, `3.13` branches and so on.

The guide I wrote:

https://devguide.python.org/getting-started/git-boot-camp/#git-worktree
#Git #worktree #CPython

@treyhunner @webology Likewise! Worktrees are useful for projects like CPython where we have `main`, `3.14`, `3.13` branches and so on.

The guide I wrote:

https://devguide.python.org/getting-started/git-boot-camp/#git-worktree
#Git #worktree #CPython

I've started migrating my repos from Codeberg to Worktree.ca; I'll keep the Codeberg repos as mirrors.

Doing this because Worktree is Canadian, and I subscribe; I felt a little bad using a non-profit's infra even though all my stuff there is open source and my CI needs are pretty minor.

EU folks: Codeberg.org is great (Forgejo).

CA folks: Worktree.ca is great (Gitea).

#codeberg #worktree #buycanadian #elbowsup #github #gitlab

I've started migrating my repos from Codeberg to Worktree.ca; I'll keep the Codeberg repos as mirrors.

Doing this because Worktree is Canadian, and I subscribe; I felt a little bad using a non-profit's infra even though all my stuff there is open source and my CI needs are pretty minor.

EU folks: Codeberg.org is great (Forgejo).

CA folks: Worktree.ca is great (Gitea).

#codeberg #worktree #buycanadian #elbowsup #github #gitlab

Thanks to a helpful person on CodeBerg, I've finally added a Canadian code repo site to my list: https://about.worktree.ca/

#github #gitlab #bitbucket #codeberg #worktree

I recently wrote a #blog article about multitasking with #git. Did you already know about the #worktree feature?

https://levelup.gitconnected.com/the-ultimate-guide-to-git-multitasking-58b2970b5b22
#Medium #programming #devops

@Schwitzd If you find you're doing this often then you can save yourself a lot of `git stash` / `git switch <branch> / `git stash pop` by using Git Worktrees instead.

Article that got me going with them https://medium.com/ngconf/git-worktrees-in-use-f4e516512feb

#git #worktree