posted in Technology
Codeberg bans vibe coded projects
cross-posted from: https://piefed.world/c/tech/p/1279028/codeberg-bans-vibe-coded-projects
Relevant .
blog.codeberg.org/protecting-our-floss-commons-from-llms.htmlposted in Technology
Codeberg bans vibe coded projects
cross-posted from: https://piefed.world/c/tech/p/1279028/codeberg-bans-vibe-coded-projects
Relevant .
blog.codeberg.org/protecting-our-floss-commons-from-llms.htmlReplying to @beep@piefed.world
A repo host that can remove your repo at any moment because someone can accuse your code of being “vibe coded” is not a repo host I’d trust. It shouldn’t matter how good, bad, or A.I. written your code is. It’s a hosting platform.
Replying to @GoatSynagogue@lemmy.world
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.
Replying to @Buddahriffic@lemmy.world
Actual question. Can you revert git to a prior state without the remote repo?
Replying to @turmacar@lemmy.world
Unless you did a shallow clone or something every repo clone is complete in git.