Dessalines@lemmy.ml to General Programming Discussion@lemmy.ml · 11 个月前Worktrees: Git's best kept secret (and why you should use them) | Tom Upswww.tomups.comexternal-linkmessage-square21linkfedilinkarrow-up121arrow-down11cross-posted to: programming@programming.dev
arrow-up120arrow-down1external-linkWorktrees: Git's best kept secret (and why you should use them) | Tom Upswww.tomups.comDessalines@lemmy.ml to General Programming Discussion@lemmy.ml · 11 个月前message-square21linkfedilinkcross-posted to: programming@programming.dev
minus-squareSpaceNoodle@lemmy.worldlinkfedilinkarrow-up3·11 个月前Yes, you should name directories descriptively. I don’t think that’s unique to repository clones.
minus-squareeldavi@lemmy.mllinkfedilinkEnglisharrow-up2arrow-down1·11 个月前definately not since that’s the way i learned. the problem is that a directory named master-hotfix-vgpool01-05022022 is very difficult to remember why it was created if you looked at it today.
minus-squareSpaceNoodle@lemmy.worldlinkfedilinkarrow-up1arrow-down2·11 个月前Something that clearly communicates its purpose.
Yes, you should name directories descriptively. I don’t think that’s unique to repository clones.
definately not since that’s the way i learned.
the problem is that a directory named master-hotfix-vgpool01-05022022 is very difficult to remember why it was created if you looked at it today.
Then clearly it was poorly named.
so what would you name it?
Something that clearly communicates its purpose.