Hi Marcus et al, If you have your GitHub account to use SSH keys, then you can skip the personal access token and use SSH keys instead. In which case you will need to use the url g...@github.com:apache/airavata.git instead of the https one.
On my Mac, since keychain remembers my ssh key password, I find the SSH based commit more convenient. Suresh > On Oct 25, 2017, at 11:14 AM, Christie, Marcus Aaron <machr...@iu.edu> wrote: > > Committers, > > The Airavata master repos are now on GitHub. To push to them you need to have > 2FA enabled on GitHub. Once you have 2FA enabled in GitHub use the following > page to make sure that you have access: https://gitbox.apache.org/setup/ > <https://gitbox.apache.org/setup/> > > Once you have access here you’ll need to generate a **Personal Access Token** > in GitHub and use that instead of a your GitHub password. Here are my notes > on how I got this to work for airavata: > > 1. Change the remote url to the https one > ``` > git remote set-url origin https://github.com/apache/airavata.git > <https://github.com/apache/airavata.git> > ``` > 2. Generate a [Personal Access Token](https://github.com/settings/tokens > <https://github.com/settings/tokens>) in Github. > 3. Give it a name. > 4. Check the **repo** scope. > 5. Create the token and copy it. (make sure to securely save this token > somewhere, you’ll won’t be able to get it back later) > 6. When doing `git push` provide the GitHub username and this personal access > token. > > Thanks, > > Marcus
