Hey #rstats, what's best practice for pushing (unfinished) commits for the sole purpose of making it available on another computer? I often switch between two computers and usually don't reach a tidy stopping point when I need to switch.
1
2
1
Use branches!
1
Thank you Dirk! Is this still considered best practice even though a commit will probably look something "have to go to office"? That is, how does one make a sensical commit history from this (or is that even worth trying?)
1
Replying to @kaioinformatics
Yep because you can rebase, or squash, or simply cherry pick. It all varies. Some of my projects have more and smaller commits (and you may find 'temp' or 'snapshot' in the commit message -- per your need here). Others (i.e. work) squash.

Dec 8, 2021 · 6:10 PM UTC

1
1
Replying to @eddelbuettel
Thanks much!
1
It's git. There are no rules. Only trial and error til we get there. And battle scars that remind us how we got there. Kidding. I love git, and yes it surely beats rsyncing between machines and messing up.
2