Dessalines@lemmy.ml to General Programming Discussion@lemmy.ml · 2 months agoWorktrees: Git's best kept secret (and why you should use them) | Tom Upswww.tomups.comexternal-linkmessage-square20fedilinkarrow-up124arrow-down11cross-posted to: programming@programming.dev
arrow-up123arrow-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 · 2 months agomessage-square20fedilinkcross-posted to: programming@programming.dev
minus-squareSpaceNoodle@lemmy.worldlinkfedilinkarrow-up3·2 months agoYes, you should name directories descriptively. I don’t think that’s unique to repository clones.
minus-squareeldavi@lemmy.mllinkfedilinkEnglisharrow-up2arrow-down1·2 months agodefinately 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-up2·2 months agoThen clearly it was poorly named.
minus-squareeldavi@lemmy.mllinkfedilinkEnglisharrow-up1arrow-down1·2 months agoso what would you name it?
minus-squareSpaceNoodle@lemmy.worldlinkfedilinkarrow-up1arrow-down2·2 months agoSomething 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.