Started using git worktree after hearing you and Prime talk about it. Was loving the workflow until I joined a team with a large mono repo. Adding a worktree is painfully slow. Unless I can find a way to improve performance, I’ll need to stick with the “old fashioned” way of creating and working g with branches.
Yep I get it. I always worked in a more or less distributed environments (with its pros and lots of cons). I wonder whether we’ll see some tooling around worktrees that simplifies the process for everyone
I have my ssh keys stored in 1Password. So when the maintenance runs, I expect that it needs the key to connect to the git repository. Which requires me to unlock 1Password.
You're so underrated man
❤️
Started using git worktree after hearing you and Prime talk about it. Was loving the workflow until I joined a team with a large mono repo. Adding a worktree is painfully slow. Unless I can find a way to improve performance, I’ll need to stick with the “old fashioned” way of creating and working g with branches.
Yep I get it. I always worked in a more or less distributed environments (with its pros and lots of cons). I wonder whether we’ll see some tooling around worktrees that simplifies the process for everyone
Good content man. Thanks!
Underrated as fu! Good content !
The problem with "git maintenance" is, that suddenly my 1password popups asking for authorization. And that I have to guess what triggers it.
That’s a strange one. Happens on every repo?
I have my ssh keys stored in 1Password.
So when the maintenance runs, I expect that it needs the key to connect to the git repository. Which requires me to unlock 1Password.
@@kris_and_ride I’d expect the job to run locally. Wasn’t aware it’s running things remotely / pulling new chnages
Seccond 🙃
I was like 214k subs then I looked again 21.4k 😅
So close....
@@devopstoolbox ya, true ... 😀
My wife left me