772

Git, invented in 2005. Programmers on 2004: (lemmy.eco.br)

submitted 4 months ago by driving_crooner@lemmy.eco.br to c/programmer_humor@programming.dev

162 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] 30p87@feddit.org 1 points 4 months ago

Huh? I'm talking about existing code being in a dir, then initting a git repo there, creating a pendant on your hoster of choice and then pushing it there. Wouldn't cloning the repo from step 3 to the code from step 1 overwrite the contents there?

[-] stembolts@programming.dev 8 points 4 months ago* (last edited 4 months ago)

There are multiple solutions to this without using --force.

Move the files, clone, unmove the files, commit, push being the most straightforward that I can summon at this time.. but I've solved this dozens of times and have never use --force.

[-] Hoimo@ani.social 3 points 4 months ago

If your remote is completely empty and has no commits, you can just push normally. If it has an auto-generated "initial commit" (pretty sure Github does something like that), you could force push, or merge your local branch into the remote branch and push normally. I think cloning the repo and copying the contents of your local repo into it is the worst option: you'll lose all local commits.