4 ms·
> To commit > Commit often These are probably the most important points here, and for pretty much any other creative process you can think of. So many good thi
by CM30 3y ago
> To commit
> Commit often
These are probably the most important points here, and for pretty much any other creative process you can think of. So many good things get lost because either nobody had a backup, or the only backup didn't work, or was from post whatever disaster nuked the system in the first place.
Source control fixes this problem, but only if you remember to use it properly in the first place.
Treat it like the save system in a video game; save and commit before any important changes, and after you do anything important in general.
- fud101 3y agoDo you branch regularly as part of this workflow?
- CM30 3y agoDepends on the project. New features and things do get separate branches that eventually get merged in once tested thoroughly, especially for website development projects. But it definitely depends. A website usually benefits from feature/bugfix branches more than a game or mod does, since the latter usually has the parts so atomised that your changes to one would have basically zero effect on any others.