Hi Yuval, My goal is more to avoid pushing to my central repo, until I'm ready, but also to provide a redundant copy of my "local" state. I suppose this could be done with pure git, by having a public central repo that is pushed to, but then a private repo that gets "blessed" commits. But I think that is over-complicating the scenario.
Essentially, I want to work locally, with lots of local commits, and then incremental pushes (using sqashed commits I believe) so the main repo has feature complete updates. BUT I want to be able to recover from a local catastrophe without losing any work. I'm wondering if I can just copy the .git directory and that's all I need, or is there a "better" git way to do this Thanks for replying. John On Jan 26, 4:20 am, Yuval Kogman <[email protected]> wrote: > Several ways to work with "uncomitted" state: > 1. commit --amend and push --force to a working branch. The commits are > overwritten each time and don't merge cleanly, but all intermediate versions > are available in the reflog. > > 2. commit small things frequently in a topic branch, and later merge these > commits into one when merging the feature. > > 3. use add --patch to commit the parts you know will stay, and don't let the > uncomitted state grow too much. > > This is not SVN, there is no reason not to commit as frequently as possible. > Committing often lets you have more choices later for merging, too. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
