Dessalines@lemmy.ml to General Programming Discussion@lemmy.ml · 17 days agoWorktrees: Git's best kept secret (and why you should use them) | Tom Upswww.tomups.comexternal-linkmessage-square20linkfedilinkarrow-up124arrow-down11
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 · 17 days agomessage-square20linkfedilink
minus-squareeldavi@lemmy.mllinkfedilinkEnglisharrow-up2arrow-down1·17 days agoevery time i do this, i have to annotate the old copy somehow. i usually use a date and months later i have no clue why i made the copy.
minus-squareSpaceNoodle@lemmy.worldlinkfedilinkarrow-up3·17 days agoYes, you should name directories descriptively. I don’t think that’s unique to repository clones.
minus-squareeldavi@lemmy.mllinkfedilinkEnglisharrow-up2arrow-down1·17 days 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·17 days agoThen clearly it was poorly named.
minus-squareeldavi@lemmy.mllinkfedilinkEnglisharrow-up1arrow-down1·17 days agoso what would you name it?
minus-squareSpaceNoodle@lemmy.worldlinkfedilinkarrow-up1arrow-down2·17 days agoSomething that clearly communicates its purpose.
every time i do this, i have to annotate the old copy somehow.
i usually use a date and months later i have no clue why i made the copy.
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.