You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whenever I create a new branch / worktree, there are some initial steps before I start working there.
Specifically, without running npm / pnpm / yarn in the worktree root, some of the VSCode plugins are not working properly:
ESLint
prettier
typescript
Jest
because these rely on node_modules which aren't copied automatically (and in most cases shouldn't be, since their versions could be different). What if GitLens+ had a setting to run such prerequesite commands for each new worktree?
I'm wondering if this is a separate issue from having VSCode workspaces pre-configured for new worktrees (#1956), or those could be solved by the same set of features.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Whenever I create a new branch / worktree, there are some initial steps before I start working there.
Specifically, without running
npm / pnpm / yarn
in the worktree root, some of the VSCode plugins are not working properly:because these rely on node_modules which aren't copied automatically (and in most cases shouldn't be, since their versions could be different). What if GitLens+ had a setting to run such prerequesite commands for each new worktree?
I'm wondering if this is a separate issue from having VSCode workspaces pre-configured for new worktrees (#1956), or those could be solved by the same set of features.
Beta Was this translation helpful? Give feedback.
All reactions