home.social

#worktree — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #worktree, aggregated by home.social.

  1. medium.com/@natescode/multitas - A super simple tutorial on #Git #worktree: `git worktree add .worktrees/hello-world/bug/fix-bar bug/fix-bar`

  2. medium.com/@natescode/multitas - A super simple tutorial on #Git #worktree: `git worktree add .worktrees/hello-world/bug/fix-bar bug/fix-bar`

  3. medium.com/@natescode/multitas - A super simple tutorial on : `git worktree add .worktrees/hello-world/bug/fix-bar bug/fix-bar`

  4. medium.com/@natescode/multitas - A super simple tutorial on #Git #worktree: `git worktree add .worktrees/hello-world/bug/fix-bar bug/fix-bar`

  5. medium.com/@natescode/multitas - A super simple tutorial on #Git #worktree: `git worktree add .worktrees/hello-world/bug/fix-bar bug/fix-bar`

  6. Good for Hashimoto 👍

    I can think of a lot of reasons to abandon #github (which is why I've moved my repos to #worktree), but lack of stability has to be one of the most objective, frustrating, and disappointing.

    theregister.com/2026/04/29/mit

  7. Good for Hashimoto 👍

    I can think of a lot of reasons to abandon #github (which is why I've moved my repos to #worktree), but lack of stability has to be one of the most objective, frustrating, and disappointing.

    theregister.com/2026/04/29/mit

  8. 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.

    https://zdrojak.cz/clanky/git-worktree-claude-code-paralelni-vyvoj-a-ai-agenti-ve-vice-vetvich-najednou/
  9. 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.

    https://zdrojak.cz/clanky/git-worktree-claude-code-paralelni-vyvoj-a-ai-agenti-ve-vice-vetvich-najednou/
  10. @TeaDrivenDev Okay, I'm done with worktrees. They're just not fully baked in terms of tooling. #git #worktree

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

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

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

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

  15. Прощай Cursor

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

    habr.com/ru/articles/1003310/

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

  16. Прощай Cursor

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

    habr.com/ru/articles/1003310/

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

  17. Прощай Cursor

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

    habr.com/ru/articles/1003310/

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

  18. Прощай Cursor

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

    habr.com/ru/articles/1003310/

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

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

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

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

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

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

  24. 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.

    github.com/wolf/dotfiles/blob/

    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.

  25. 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.

    github.com/wolf/dotfiles/blob/

    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.

  26. I use . A feature of Git I leverage heavily is . 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 suck by the way), hooking up `.envrc` if you use (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 . (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.

    github.com/wolf/dotfiles/blob/

    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.

  27. 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.

    github.com/wolf/dotfiles/blob/

    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.

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

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

    habr.com/ru/companies/ruvds/ar

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

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

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

    habr.com/ru/companies/ruvds/ar

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

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

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

    habr.com/ru/companies/ruvds/ar

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

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

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

    habr.com/ru/companies/ruvds/ar

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

  32. 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

  33. 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

  34. 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

  35. 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

  36. 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

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

    bojidar-bg.dev/blog/2025-10-24

    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

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

    bojidar-bg.dev/blog/2025-10-24

    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

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

    bojidar-bg.dev/blog/2025-10-24

    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

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

    bojidar-bg.dev/blog/2025-10-24

    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

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

    bojidar-bg.dev/blog/2025-10-24

    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

  42. 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.

    git-scm.com/docs/git-worktree