As I began my Python journey I needed a text editor and Atom by GitHub (I also will use) seemed like a great tool. I learned however that it is mostly written for programmers with a set of knowledge I did not yet have. I started out using Atom locally on my MAC and it worked great. I ran into confusion and documentation gaps when I tried to add GitHub so that I can get the value that the tool brings. I gathered the steps together perhaps someone else searching for them or the Atom documentation team can use the following. While Atom has native support for GitHub there are a couple of steps needed to activate it. First, there are a few places to begin if you are new to Atom:
Start in the section of the Flight Manual called “Atom Basics”. On subjects like that, the documentation is useful as the Flight Manual automatically adjusts to your OS, pretty cool right.
1. Have an account set up on GitHub with a repository created
2. in Atom, the Command Palette. If you press Cmd+Shift+P while focused in an editor pane, the command palette will pop up.
3. To clone a repository, run the `GitHub: Clone` command. In the dialog paste a URL of a repository and click “Clone”. A new project will get added to the Tree View.
The auth token has nothing to do with Atom’s git integration. It’s specifically for accessing the GitHub API so that the `GitHub` package can display pull requests. You do not need a token to interact with your repositories
To start a new repository, the best way as novice git users is to open it via the GitHub site and use the clone feature to create your local repo. If you have an initialized git folder with code, and especially if you’ve tried to make commits and want to keep them, then you may need to use the CLI to fix the remotes so that your repository points at the one you have on GitHub’s servers, or you can clone a completely blank repo and paste in your new files. Commits and pushes can all be made inside Atom without installing anything extra, but for advanced usage, you might want the `git-plus` package.
Atom and GitHub only talk to one another under specific circumstances: when you push to or pull from a repo stored on GitHub’s servers, or when you have a repo stored on GitHub that has pull requests. The GitHub auth token is used only for this latter interaction. Before you can push to your repo, you need to tell git (any instance of git, because they’ll all store the credentials in the same location on your computer, so there’s no need for worry about compatibility between Atom and CLI git) what your GitHub username and password are.
If you’re doing it with the `GitHub` package, Atom will simply [ask you](https://github.com/atom/github/blob/a70b71356c471167283bfaa6ee71d1d9041ef8df/lib/views/credential-dialog.js). If you’re using the CLI, it will ask you. GitHub’s site has [additional relevant documentation](https://help.github.com/en/articles/caching-your-github-password-in-git) for different OSes and authentication methods, in case your team wants to use SSH.