In the SSH Private Key field, specify or navigate to the path of the SSH key that is linked to your GitHub repository.
To create an SSH key, see GitHub help.
While creating the SSH key, do not provide any paraphrase. There is a known issue with keys with password, which will be fixed in the next update.
After the SSH key is created and added, test your SSH connection. For more information, see GitHub help.
A message confirming the successful addition of the SSH key appears at the lower-right corner of the screen.
In the Local Path field, specify the project path.
The project path must be different for each of the following scenarios:
- Adding a project to GitHub: Provide the path of the project you want to add to your GitHub repository for version control.
- Opening a connection: Provide the path to an empty local folder in which the GitHub project is to be cloned locally.
Open the project that you want to add to GitHub. This is the same project for which you specified the path while creating a GitHub connection. For more information, see Step 8 in Create a GitHub connection.
After pushing files, if you receive the following message, it indicates a merge conflict in the files:
“The tip of your current branch is behind its remote counterpart. Try pulling before pushing.”
To merge conflicts if the changes are made in the same file:
- Choose Edit > Preferences > Version Control.
- Provide the path of the .exe file of any External Diff/Merge Application.