Dessalines@lemmy.ml to Programming@programming.dev · 2 months agoWorktrees: Git's best kept secret (and why you should use them) | Tom Upswww.tomups.comexternal-linkmessage-square22fedilinkarrow-up190arrow-down11cross-posted to: git@programming.dev
arrow-up189arrow-down1external-linkWorktrees: Git's best kept secret (and why you should use them) | Tom Upswww.tomups.comDessalines@lemmy.ml to Programming@programming.dev · 2 months agomessage-square22fedilinkcross-posted to: git@programming.dev
minus-squareDessalines@lemmy.mlOPlinkfedilinkarrow-up8·2 months agoIf they’re untracked files anyway, that’s unavoidable.
minus-squareKubeRoot@discuss.tchncs.delinkfedilinkEnglisharrow-up0·2 months agoIf they’re ignored files, setting them up locally won’t end up in the repo. If you put a symlink into the repo, fixing that for your setup will register as a change within git, which can cause annoyance and even problems down the line.
minus-squareMartin@feddit.nulinkfedilinkarrow-up4·1 month agoI don’t think anyone suggested that you add the .env symlink to the index. It should be ignored by git.
If they’re untracked files anyway, that’s unavoidable.
If they’re ignored files, setting them up locally won’t end up in the repo. If you put a symlink into the repo, fixing that for your setup will register as a change within git, which can cause annoyance and even problems down the line.
I don’t think anyone suggested that you add the .env symlink to the index. It should be ignored by git.