Нажимаем на стрелку внизу, и мы попадем в меню. В нем вставляем ссылку на репозиторий созданий ранее:

Если репозиторий пустой все пройдет как надо. В моем случае там уже лежит один проект созданий специально чтоб вызвать ошибку. Он не имеет с этим ничего общего, даже файлы разные.
Выходов из ситуации несколько, я рассмотрю только один из них — создание новой ветки [другой путь разработки, тестовый полигон. По умолчанию установлена ветка “master”] в репозитории для этого делаем следующее:

Может возникнуть вопрос – Что значат другие иконки?
Ответ:
Карандаш для того чтоб фиксировать изменения локально (commit). Используйте когда есть что сохранить, то есть код или файлы изменились.

Все остальные тоже играют важную роль:

Дополнительно:

Чтоб GitHub верно отображал русские комментарии (если есть) при просмотре кода через сайт нужно сделать следующее:

Cоветую всё-таки изучить Git Bash.

Я старался писать как можно понятнее, если что-то не так, то поправьте в комментариях!
На этом все. Спасибо за внимание!

Данная статья не подлежит комментированию, поскольку её автор ещё не является полноправным участником сообщества. Вы сможете связаться с автором только после того, как он получит приглашение от кого-либо из участников сообщества. До этого момента его username будет скрыт псевдонимом.

GitHub Extension for Visual Studio

The easiest way to connect to your GitHub repositories in Visual Studio

By downloading the extension you agree to the End-User License Agreement

Requires Windows and Visual Studio 2015 or newer

Easy Installation

When you install Visual Studio, select the option to Customize the install and be sure to check the GitHub Extension for Visual Studio check box. It’s that easy.

Did you already install Visual Studio without adding the extension? No worries, download it now.

Connect to GitHub

Once you install the extension, you can log into your GitHub.com or GitHub Enterprise account in Visual Studio with full support for two-factor authentication. There is no need to use personal API tokens.

Clone repositories in one click

Once connected, it’s quick to clone repositories from your account or any organization you belong to.

Click the clone button to bring up a dialog that shows all the repositories you have access to. Use the filter textbox to quickly find the repository you’re interested in.

Create repositories and build something great

Need a new repository on GitHub? No problem! The create dialog makes it easy to create a repository on GitHub and clone it to Visual Studio all in one step.

Publish your local work to GitHub

Already have a project on your machine? Well what are you waiting for? Publish it to GitHub and start collaborating with others.

In the Team Explorer window, click on the Sync tab to get to the Publish to GitHub dialog.

View Pull Requests in Visual Studio

View all of the Pull Requests for your project in the GitHub pane, and sort and filter them by Open/Closed state, Assignee and Author.

Open the GitHub pane by typing GitHub into Visual Studio Quick Launch (Ctrl+Q).

Create Pull Requests from Visual Studio

Turn a branch into a Pull Request directly from Visual Studio.

In the GitHub pane, click the Create New link to create a new Pull Request on GitHub.

Create Gists

Create gists and upload them to GitHub directly from Visual Studio.

Simply select the code to upload and select Create Gist from the GitHub context menu.

Connecting to Github with SSH (Windows)

Pre-requisites

When to use SSH keys instead of HTTPS

• Your corporate firewall blocks port 22, then even if you have set the remote origin to use HTTPS url, the authentication will fail as it is done via SSH.

Remedy is to set up SSH keys and use SSH over HTTPS port 443.

Below are some of the errors different applications throw when the port is blocked and HTTPS remote url is used.

Git Bash

When you try to push your changes, both Github Login and OpenSSH prompt asking for your username and password will fail with error remote no anonymous write access. fatal authentication failed for github .

Github Desktop Application

You will be able to login to your github desktop application as the authentication is done via HTTPS. However, when you try to push your changes it will result in authentication failure.

Below is the logs captured by the desktop application showing that the git push is trying to authenticate via SSH.

Generate new SSH key

Generate SSH key with your email id as comment.

When you’re prompted to “Enter a file in which to save the key,” press Enter to save the key in the default location (/c/Users/username/.ssh/id_rsa). Your public key will also get saved here.

Copy the public key to clipboard.

Add public SSH key to your GitHub account

Go to Settings in your Github account to add the SSH public key.

Under SSH keys tab, select New SSH key .

Give a title and paste the key in the text area.

Add private SSH key to the ssh-agent

Git bash tool comes with a ssh-agent.

/.bashrc file by running below command in git bash.

Paste below script into your

/.bashrc file to auto launch the ssh-agent whenever you run your git bash shell.

This script will load the identities in the ssh agent from your default location

Use SSH over HTTPS

This step is required only if your corporate firewall is blocking port 22.

Create a new config file in your .ssh directory i.e. /c/Users/username/.ssh/config

Paste below contents in the file to use port 443 for SSH connections to host ssh.github.com .

Run below command in git bash to verify that the configuration is working. Ignore any authentication failures.

You can see that the SSH connection is now established via port 443.

Verification

To check if everything works as expected perform below steps:

Run new git bash shell.

Check if the identity has been added to the ssh agent.

• Check that the key is being used by trying to connect to git@github.com.

• Clone the repo using the SSH url.

Going forward, every push/pull will use the SSH keys to authenticate with Github.