Git/GitHub problem...saving to same repo?


#1

Yes I’m a noob. I’m currently in a Codecademy intensive program. I’m having a problem w all the projects I’ve pulled to GitHub keep going to the same repo, when I’ve been trying to have separate repo’s for each project, just to practice. It would be much easier to show someone on slack but I’m not sure who would help considering I don’t know a general workspace to get into to ask. I have 11 repo’s and the last 5 of them have went to the same repo? I’ve tried to ‘reset’ git and have searched foooorrever and can’t find any answer, so any help would be greatly appreciated and if someone would be able to get on slack that would be even better. I also dont know if I should put my slack info on here, so I’ll wait for a response. Gotta luv the noobs lol. Thx in advance


#2

I suggest doing all git stuff in the command line before letting Atom handle it. You will learn it a lot better and be far more comfortable if something goes wrong on the Atom side.

I’ve never heard of this issue either, so it’s likely you set up the local git repos wrong. In the command line, you may want to run git remote --verbose on each local repo to see what they are synced with.


#3

Yeah, I have been using Git Bash for my projects and GitHub of course to practice the standard workflow of it all but I know I’m just in over my head. I agree that I have a lot of things messed up and trying to explain what I don’t know what’s wrong is impossible, especially for a noob lol. That’s why I need someone to look over what I have going on over here, mainly my local file setup and my Git. I feel like Git is all messed up with add’s, push’s, etc. I wish I could just start all over. Thanks for your response and I will def try what you said. I actually ended just copying and pasting my code from atom onto github lol, just to turn it in for review.


#4

Is there a website like slack for community members to look and review others work? Or how do I get into a workspace on slack where I can get some help the same way?
Or maybe I’ll just start over with new local files and see if that helps.


#5

There are forums dedicated to coding and specific coding topics, such as the GitHub community forum, and there are Q&A boards like Stack Overflow (and the many sites that spawned off of it).

If you have the latest version of the code on GitHub successfully, then there is no harm in deleting the local files and using git clone to re-establish the local repo. If you run git remote --verbose in each of the problematic repos, you should be able to see what’s wrong. You can use git remote remove <name> and git remote add <name> <url> to fix it manually, which would be a good learning process, but if you stick with git you’ll pick that up eventually anyway, and right now the most important thing is making sure that your code goes where it needs to go, so if deletion and git clone can get your code the way you want it to be, do that.

For starting a new repo, the fastest way is to open a repo on GitHub and clone it. You can (and I sometimes do, because I’m insufficiently work-averse) run git init and git remote add first, then go to GitHub, start a repo, and run git push -u origin before you do anything else, but that’s not efficient. For best results, you should start a project on GitHub and treat the GitHub-hosted repo as canon. Any local repo you have is just a reflection of the true Platonic form of the code project that lives in The Cloud.


#6

This post was flagged by the community and is temporarily hidden.