3 ms·

> are people using git without frequently pushing to remote? I feel like having a remote backup of my work in progress is the killer feature. I use git without

> are people using git without frequently pushing to remote? I feel like having a remote backup of my work in progress is the killer feature. I use git without a remote pretty often. When doing personal projects or exploratory work, the problem is either so trivial that I don't care about backup, or already backed up using something like Nextcloud/Syncthing. But having the commit history allows me to easily look at old code, revert changes, and make big structural changes without having to back up the entire project folder in case I end up disliking the new structure. I guess you're just not working on many things at a scale where version control is useful but setting up an online repo doesn't seem worth the time.

Waterluvian 6y ago
When I do exploratory research, having a history of commits, days, months, years after the end of the research project is invaluable for many possible future needs. I’m still not sure I see a strong case for not bothering with a remote. But I appreciate we all do things at different fidelities.
perryizgr8 6y ago
> I guess you're just not working on many things at a scale where version control is useful but setting up an online repo doesn't seem worth the time. It is literally a couple of clicks to set up a private repo on github. For me, either the problem is too small to set up git, or it is big enough to spend half a minute to create a github repo.
- panpanna 6y ago
  Pro tip: you can set up a remote repo on any Unix machine with SSH access: ssh machine "mkdir x; git init x" git clone machine:x If you have something sensetive or just want to avoid github/gitlab for some other reason, an empty remote container with SSH access works just as well.
samus 6y ago
You could just set up a private Github monorepo for all your utility projects and experiments. One branch per project, and you check out exactly the branch you want. Since 2012, `git clone` supports `--single-branch`, which makes it download only the commit history of that specific branch.

Waterluvian 6y ago

When I do exploratory research, having a history of commits, days, months, years after the end of the research project is invaluable for many possible future needs. I’m still not sure I see a strong case for not bothering with a remote. But I appreciate we all do things at different fidelities.

perryizgr8 6y ago

> I guess you're just not working on many things at a scale where version control is useful but setting up an online repo doesn't seem worth the time. It is literally a couple of clicks to set up a private repo on github. For me, either the problem is too small to set up git, or it is big enough to spend half a minute to create a github repo.

panpanna 6y ago
Pro tip: you can set up a remote repo on any Unix machine with SSH access: ssh machine "mkdir x; git init x" git clone machine:x If you have something sensetive or just want to avoid github/gitlab for some other reason, an empty remote container with SSH access works just as well.

samus 6y ago

You could just set up a private Github monorepo for all your utility projects and experiments. One branch per project, and you check out exactly the branch you want. Since 2012, `git clone` supports `--single-branch`, which makes it download only the commit history of that specific branch.