Github Confusion

Have you ever had an issue with GitHub where your commits were not reflecting on the website repo, but your commits kept disappearing like they were committed? Did you visit Stack Overflow and still could not find a solution?

Well, this article might just be able to help you. I had this same issue for the past three months and it only just took me a space of two hours or less to resolve after of course trying multiple solutions over the past months.

Here's what the problem was, my actual repo was buried under two file layers, each with the same name as the said repo (I have no idea how I got in that tangle). This means if I tried committing on the first, I would get the {fatal: not a GitHub repo} error, then I changed to the second layer and it would commit without error messages and would continue my work. I did not notice its absence on my website repo till I got kicked out of boot camp as they assumed based on what my GitHub reports were, that I had not been doing my tasks.

Today I decided to address the issue and discovered the whole layering thing, here's how I handled it {In case you were wondering where those commits were, turns out they were all just on my local machine}. First, I renamed the first layer to avoid further confusion, created a file on the second and committed, and sought it out on the website repo, still could not find it. Used the "cd" command to go into the next layer and pasted the file I had just created on it, did the whole git process and voila!! There it was, on the website repo.

These are my corrections, take note of your file paths to know where your errors start. Always open a new file in your repo folder, not in the main folder; say your main folder is DRM, next is ARM and repo is CRM, do well to navigate into CRM before creating a new file for your work. Also, do not give the exact names of your repo to the folders you clone them into. Always crosscheck your repo with your just committed work to ensure visibility {don't be like me}.

If you do have any questions for me, do well to drop them in the comments, as well as tell me if this article has helped you in any way. Cheerio!