Cant finish github sharing process что делать

Can't finish github sharing process [duplicate]

I’m trying to share one of my IntelliJ projects on GitHub, but whenever I try to do that, I get an error that says it successfully created the project but initial commit failed. It gives me instructions on how to fix this, but I have no idea what the instructions mean. Can anyone decipher the error and tell me what to do?

Here is the error:

1 Answer 1

Basically, before you can create a commit, git needs to know who you are and how to refer to you. To tell git who you are, run the following commands.

Set the user name:

After that you will be able to create commits. Probably you can just rerun whatever you did that lead to this error.

Вопрос №50804 от пользователя Кирилл в уроке «Рабочий процесс», курс «Введение в Git»

сделал так, как надо, но он не хотел принимать, постоянно выводил ошибку.Из-за этого подсмотрел решение учителя. Я сначала думал, что проблема во мне, а оказывается, лыжи не едут. Не проходит даже решение учителя

Хорошо что я сразу зашел в обсуждения, такая же история

Решение учителя технически не может не работать, так как он попросту не собралось бы. Можете уточнить что именно у вас не работает. Я сейчас в упражнении выполнил команды из решения учителя и всё в порядке. Обратите также внимание на предупреждение При выполнении задачи состояние репозитория могло измениться. Перед набором команд из списка, обновите упражнение с помощью кнопки Сброс.. После этого попробуйте заново последовательно скопировать поочередно строки из решения учителя в терминал и выполнить их.

Станислав Дзисяк, все прошло, это я затупил 🙂

Попробовал сбросить всё. Однако, пишет, что я что-то сделал не правильно. Я прошёлся по каждой строчке кода, но всё равно то же самое. Не понимаю. Главное, в самом терминале всё проходит правильно

make: Entering directory '/usr/src/app'

FAIL tests/index.test.js

✓ test-teacher-git (18 ms)

✓ test-user-git-start (4 ms)

✕ test-user-git-finish (6 ms)

Test Suites: 1 failed, 1 total Tests: 1 failed, 2 passed, 3 total Snapshots: 0 total Time: 0.676 s, estimated 1 s Ran all test suites.

How to fix — git@github.com permission denied (publickey). fatal could not read from remote repository and Support for password authentication was removed. Please use a personal access token instead

One of the easiest ways for you to generate a key pair is by running ssh-keygen utility.

Open the command prompt and type in the following

(Note — If you do not have ssh-keygen installed on the window then Click here.)

To keep the ssh-keygen simple, do not enter any key name or passphrase.

Where to find the key pair

The file will be generated at — /Users/rahulwagh/.ssh/

Name of the file — id_rsa.pub

(To generate SSH keys on Windows machine click here)

Step 2 — Adding SSH key to your GitHub account

1. Goto your GitHub Account -> Settings

Git hub account settings

1. Then look for SSH and GPG keys under **Account Settings -> SSH and GPG keys **

github ssh and gpg keys

1. After that click on New SSH Key. Assign some meaningful name to your key

GitHub new ssh keys

1. To get the key goto to your command prompt and switch directory path

Windows — C:\Users\rahulwagh.ssh\id_rsa.pub

Linux — /Users/rahulwagh/.ssh/id_rsa.pub

Run the following command

Copy the content of the key

Paste the key inside your GitHub account

Git hub account settings

Now you can clone your GitHub repo and it will not complain about git@github.com permission denied (publickey). fatal could not read from remote repository

Benefits of this approach

1. You do not need to supply you GitHub Username and password
2. More secured

Drawback

1. The process of generating SSH keys is little troublesome.
2. If you switch your laptop/desktop then you need re-generate the SSH keys again and perform the same steps onto your new laptop/desktop.

Approach 2 : Using GitHub HTTPS urls

This is one more approach in which you do not need to worry about SSH key generation.

You need following —

1. GitHub repo URL with HTTPS (Ex — https://github.com/rahulwagh/example.git)
2. Your GitHub Username
3. Your GitHub Password

Run the following command to set git remote

After that it will ask for your username and password , supply your username and password.

Once you are authenticated then you can perform your Git operations.

Benefits of this approach

1. You do not need to generate SSH keys
2. You do not need to copy your SSH keys to GitHub accounts
3. This approach can be used from any Laptop, Desktop. You only need to provide your GitHub credentials with this approach.

Drawback

1. The only drawback which I can see is you need to input your GitHub credentials everytime.

2. GitLab: How to fix gitlab.com: permission denied (publickey) fatal: Could not read from remote repository

2.1 Multiple public keys inside

When you are working with multiple github repositories then there is high probability that you might have incorrect public key mentioned inside your

For example I have generated the public key for my GitLab project by the name

But when I checked my

/.ssh/config file I noticed the incorrect name of public key for the gitlab.com

Here is the content of my

/.ssh/config file where the public key name is

/.ssh/id_rsa instead of

How to fix?

To fix this issue you should correct the public key name —

3. Bitbucket — Permission denied (public key), can’t clone/clone to bitbucket

There could be multiple reasons behind the issue —

3.1 You did not add your local SSH keys to BitBucket Settings

SSH keys could be one of the most probable reasons which are causing the issue while working with your BitBucket repository.

You might see the following errors —

or (In case you are working with mercury then you might see this error message)

How to fix?

Before we start debugging the issue, let’s first debug the issue to know the exact reason behind this error.

Run the following command from your terminal (put your correct repository name) —

The above command should return you with Username and in case you did not see your username then you need to Create SSH keys and add to your BitBucket account.

Step 2 — Goto Your Account -> Manage Account -> SSH Keys

Step 3 — Click on Add Key

Step 4 — Paste your key which you have generated in Step 1.

Step 5 — Finally click on Add Key

It should work after adding the SSH keys to your BitBucket account.

(Note — Here are some official links from bitbucket if you are interested more — click here)

3.2 Permission on your bitbucket directory

There could also be a possibility that you do not have permission to access the BitBucket repository. Check with your bitbucket administrator with regards to your permission.

If it is the case of permission then your bitbucket administrator could grant the permission.

1.1 Generate ssh-keygen on Windows 10

If you are working on a windows machine then you need to install the OpenSSH .

Goto: Apps > Apps and Features > Manage Optional Features

Verify the list of the apps, if it already installed. If not then go at the top of the page then select Add a Feature afterwords —

• OpenSSH Client : Locate OpenSSH Client , then click Install .
• OpenSSH Server : Locate OpenSSH Server , then click Install .

Install OpenSSH using PowerShell on Windows 10

If you like using Powershell then first make sure OpenSSH features are available to install —

Copy and run the following command

After that install server and client features using the following command —

1.2 Verify OpenSSH client is installed

1. Goto settings panel

windows setting panel

1. Click on Optional Features and then look for OpenSSH client, if you can find the OpenSSH client which means you have installed it correctly.

windows setting panel

1.3 Generate ssh keys on windows 10

1. Next we need to run the ssh-keygen and for that goto window’s command prompt and open it in administrator mode.

windows command prompt administrator mode

1. In the command prompt type the following command

1.4 Where to find the key pair

The file will be generated at — C:\Users\rahulwagh.ssh\id_rsa

Name of the file — id_rsa

4. How to fix(GitHub)-Support for password authentication was removed. Please use a personal access token instead

GitHub has recently announced their migration to use token-based authentication which means you can no longer use your username and password for GtiHub authentication. You need to create personal access token to continue use of your GitHub Repository.

Here is my private GitHub repository which I was trying to clone and prompted with the error message —

Support for password authentication was removed. Please use a personal access token instead

Before fixing the issue lets try to understand how do you clone your Git Repo — https:// or git@github.com

This issue is very much dependent on the way you clone your repository.

1. git@github.com:rahulwagh/jhooq.git — If you are using SSH way of cloning the repository then you will not face issue related to personal access token. Because when you use SSH way of clonning then you should always create SSH Keys and copy public SSH key to GitHub SSH and GPG keys

2. https://github.com/rahulwagh/jhooq.git — If you are using HTTPS way of cloning the Git Repository then you will be prompted with username, password and after entering the username and password you will be thrown with error Support for password authentication was removed. Please use a personal access token instead

How to fix the personal access token for GitHub Repository

1. Login to your GitHub account from the web browser.
2. Goto -> Profile Pic -> Setting

personal access token settings

1. After that you should look on the left navigation panel and there should be an option of Developer Settings

personal access token settings developer settings

1. Aftr that it will redirect you to the new page where you will find an option Personal Access Token in the left navigation. You should click on it —

personal access token click on the option

1. Then next on the right side of the screen you have an option to Generate New Token —

personal access token Generate new Token

1. Enter the token name along with the scopes —

personal access token enter token name and scopes

1. Finally Generate Token
2. Now Copy the generated Token

personal access token copy generated token

1. Go back to terminal and re-issue the Git Clone command and instead of password input the access token

supply personal access token instead of GitHub password

It should fix your issue of — “Support for password authentication was removed. Please use a personal access token instead”