- cross-posted to:
- programming@programming.dev
- cross-posted to:
- programming@programming.dev
cross-posted from: https://piefed.world/c/tech/p/1279028/codeberg-bans-vibe-coded-projects
cross-posted from: https://piefed.world/c/tech/p/1279028/codeberg-bans-vibe-coded-projects
IMO everyone should have a local backup of everything they can get related to the repo. Like I know with git itself, anytime you clone the repo you get everything, but also the supporting stuff that is in the layer outside of git. IMO the host should mainly be the hub where everyone gets and interacts with the project, while everything else is already good to go in a new location, should the host either screw up in good faith, get corrupted by outside influences, or gets overrun by local or remote powers.
This makes me a bit curious about whether the overall risk to projects is higher from individual local device failure or politics around who controls remote hosting services and the nature of the project.
Actual question. Can you revert git to a prior state without the remote repo?
Yes, that’s a core purpose of git.
git reset --hard <commit-hash>
Yeah, as the other commenter mentioned, git is a distributed source control system, so all clones have the full history (though you can bump up the “starting point” to reduce the overhead of storing all previous commits).
Hosts like github can add more features on top of that, which would have to be backed up separately, but you can automate the repository itself using a single command, which is the same command used to make a clone in the first place.