5 ms·
Honestly it's a mess. I still do unwieldy naming schemes like: PROOJECT1-FINAL-WORKING-COPY-A PROJECT2-NEW-FINAL-V1 PROJECT2-NEW-FINAL-V2 But once
by legrande 3y ago
Honestly it's a mess. I still do unwieldy naming schemes like:
PROOJECT1-FINAL-WORKING-COPY-A
PROJECT2-NEW-FINAL-V1
PROJECT2-NEW-FINAL-V2
But once it's on Github, it automatically gets version controlled, so I can roll back to a working state if I make a mistake.
- blackhaj7 3y agoOh I have plenty of project-name-new-newer-newests!
- JohnFen 3y agoI have taken to just using git's local repository. That way my version control history stays local with the project itself. I've found it to be a lot easier to manage that way than having a central repository that holds all my projects. Although I'm considering moving away from git to a different version control system, so this may change.
- interbased 3y agoI had this same issue when working with Jupyter notebooks during my data science days, but after getting used to using GitHub on a team, all my code is just neatly organized in separate folders/repositories and every update is committed. It's fairly effortless now.