Desktop & laptop workflow anyone?

Sometimes you want to keep working but you just don't want to sit at your desk anymore. I work at a desk at work, and then come home and sit at my desk to continue working on my game.

Does anyone have a good workflow for using a laptop that doesn't involve committing changes to push to the other device? I used to push commits on a random branch and say things like, "Switching to laptop" but then realized that those commit messages are included when merging back to master. Blegh.

 

Are you using git? You can commit and push, then fetch and reset your branch fairly trivially.

It's a lot more intrusive with Mercurial, and not recommended, but git is absolutely made for this workflow.

Otherwise, why do you care about extra commits? I do it all the time and just mark them as <WIP> so I know they aren't necessarily "complete" in and of themselves.

 

It clutters up the logs and I don't like that. It's not multi-developer friendly.

You basically recommended the exact workflow I specified I'm trying to avoid.

 

... do you even git?!

If you reset your branch and continue working on the new machine, you can just delink the old dead end and forget about it. It precisely does NOT clutter the log, and it is very multi-developer friendly.

Seriously, git is used to develop the Linux kernel. Last I checked there is more than one person working on that project, and they are distributed around the globe pretty widely.

 

Yeah, I use and abuse git all the time that way. I would rather take the time to fix a git problem, than copy a folder over manually, any day of the year.

 

I cannot work anymore without source control. Even if I am making a simple script to do a one-time job, I still fire up a git repo in the work directory and commit early and often. It allows me to confidently try out anything that springs to mind. It is what git is MADE for.

Working without source control is like playing a console game without a save cartridge. Savage!

 

Plus, how many times has the project gotten corrupted somehow using Unity? For source control users, it turns a potential catastrophe into a simple inconvenience.