Dessalines@lemmy.ml to Programming@programming.dev · 3 个月前Worktrees: Git's best kept secret (and why you should use them) | Tom Upswww.tomups.comexternal-linkmessage-square22fedilinkarrow-up1121arrow-down11
arrow-up1120arrow-down1external-linkWorktrees: Git's best kept secret (and why you should use them) | Tom Upswww.tomups.comDessalines@lemmy.ml to Programming@programming.dev · 3 个月前message-square22fedilink
minus-squareEager Eagle@lemmy.worldlinkfedilinkEnglisharrow-up6arrow-down1·3 个月前Then we have the “it works on my machine” issue. I’m vehemently against symlinks pointing out of the code repository because of that.
minus-squareDessalines@lemmy.mlOPlinkfedilinkarrow-up10arrow-down1·3 个月前If they’re untracked files anyway, that’s unavoidable.
minus-squareKubeRoot@discuss.tchncs.delinkfedilinkEnglisharrow-up3·3 个月前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.
minus-squareMartin@feddit.nulinkfedilinkarrow-up4·3 个月前I don’t think anyone suggested that you add the .env symlink to the index. It should be ignored by git.
deleted by creator
Then we have the “it works on my machine” issue. I’m vehemently against symlinks pointing out of the code repository because of that.
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.