Course Content
GitHub Fundamentals
GitHub Fundamentals
Pushing Changes
Push Attempt
Previously, the README file was modified and the changes were committed locally. Let's send these changes to your remote repository. In a basic scenario like this, a simple git push command is sufficient:
The git push command uploads local repository content to a remote repository, synchronizing changes made locally with the remote branch.
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.
GitHub switched to personal access tokens to enhance security and improve access control. Tokens have an expiration date and a specific set of privileges, unlike regular passwords, which reduces the risk of credential compromise and allows for more precise permission management.
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!
Thanks for your feedback!
