Notice: This page requires JavaScript to function properly.
Please enable JavaScript in your browser settings or update your browser.
Pushing Changes | Introduction to GitHub
GitHub Fundamentals
course content

Зміст курсу

GitHub Fundamentals

GitHub Fundamentals

1. Introduction to GitHub
2. Basic Interaction with Remotes
3. More Advanced Workflows

bookPushing Changes

Push Attempt

In the previous chapter, we modified the README file and committed the changes locally. Let's now send these changes to our remote repository. In a basic scenario like this, a simple git push command is sufficient:

Oops, something went wrong and authentication failed. Let's try again:

As you can see, even after entering the username and password for the GitHub account, authentication still failed. The error message indicates that GitHub has discontinued password authentication for operations on repositories.

Personal Access Token

Instead of passwords, GitHub now requires the use of more secure methods like personal access tokens.

Let's now create one by following the instructions in the video below:

Once you've copied and written down your token, let's try pushing the changes again. Now, you should enter the token instead of your password.

Congratulations on your first successful push to the remote repository!

What is one of the main advantages of using GitHub personal access tokens over passwords?

What is one of the main advantages of using GitHub personal access tokens over passwords?

Виберіть правильну відповідь

Все було зрозуміло?

Як ми можемо покращити це?

Дякуємо за ваш відгук!

Секція 1. Розділ 6
some-alt