• 0 Posts
  • 14 Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle





  • yeah, I think these are the main hurdles for me:

    1. Untracked files are not copied

    When you create a new worktree, it is created from whatever is comitted, so gitignored or uncomitted files are not copied.

    So if you have .env files, you have to copy them over manually. And for dependencies, like for example node_modules, you would have to run npm install again in the new worktree.

    Mainly .env files, as they are handcrafted. And:

    1. Editor / IDE complexity.

    A few projects I work on are multi-root (using VS Code terminology) and that’s already complex enough. Adding worktree directories means adding a level to that, which I’m not bought in. And I don’t want a separate workspace for each branch I work on, that just shifts the complexity from git to the IDE / editor.




  • That happens when I select the wrong kernel in the systemd boot menu, before that screen. Doing nothing after an upgrade also selects the wrong version by default, it’s kinda annoying. I have to select the most up to date version and press Ctrl-D to make it the default on the next boot.

    If that’s also what happens here, maybe a solution could be to keep only one kernel version and its fallback. But idk if you’re using systemd-boot or grub