Issues linking Github Desktop to Atom...

[JohnYingling]

Having some serious problems here linking my Desktop Github to Atom.

Install seemed fine. What on earth is going on here?

[JustineEvansUM]

Woah, @JohnYingling, what did you do? Crazy.

First thing's first, try removing your Project folder from Atom. Simply right click and select 'Remove Project Folder.'

Next, let's try re-initializing over the top of your current GitHub Repo. In the GitHub App, right click on your repo folder and 'remove it.' Click through the warning message.

Next, select 'Add a local repository' and locate your full repo path, like /john/homework/web-dev-hw. Press 'Fetch origin' at the top menu bar and see if you receive an error.

Then get back to me.

[JohnYingling]

That worked without blowing up on me....but...I mean, I got no glaring error, but I still feel like I'm missing something.

I don't have both the "uncommited changes" box you are talking of, or the option to "Publish Repo" and I'm not sure why. Combed through everything multiple times.

Screens attached.

[JohnYingling]

Wait wait, did I already do this?

I actually made this on Github's site first...but did it connect? I think it did! I can view my .readme!

I clicked "view on Github" in the Desktop app and it brought me here...

[JustineEvansUM]

I think you're moving in the right direction, for sure. Try making a change to file, like your README, or even creating an index.html (just through in a few characters) and save it. Make sure you save the files, or the App won't recognize changes.

[JustineEvansUM]

PS - I see a space in your screenshot filename... Watch out! That will be hard to link!

[JohnYingling]

@JustineEvansUM Why would it be hard to link? Do you mean add to my Readme, or will I run into problems later?

Added to the readme already... will note this advice! :)

[JonSwallow]

@JohnYingling You do have it connected according to your picture. To make a change you have to fill out the summary and description then you can commit. The button that says fetch origin will change to push to origin.

[JustineEvansUM]

@JohnYingling and class, here's an Issue from your classmate of where a space in a filename can cause problems!

Working spaces is largely a graphical interface perk of operating systems, but it's not allowable in all coding. For example, I work natively, building my sites in full before pushing them to a server. Here's a shot of my CLI or command-line interface (which is Terminal for macOS). You'll see I can't change my directory to the folder "My Cool Files." It doesn't even recognize it - "No such file or directory." If I want to access the folder, I have to use a \ to tell the system there's a space there. It gets really messy, believe me.

In other words, don't use spaces. You'll thank yourself later!

[mjohnson92]

This was really helpful, I had very similar issues just in different order. Thank you!

[tannercurey]

Thanks, I also found this issue helpful as I has similar problems.

[JohnYingling]

Sorted.