You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The following section shows commands that push a change to github using an access token and checks status after the push.
I have, without problems, run similar commands for years with password supported access , and I believe it also ran without problems once with the access token.
If I clone the project I get all changes, so it seems that my only problem is to move the remote pointers in the existing project.
Ib@DESKTOP-R2E4N8B ~/GitHub/pagaten
$ git status
On branch master
Your branch is ahead of 'origin/master' by 1 commit.
(use "git push" to publish your local commits)
nothing to commit, working tree clean
Ib@DESKTOP-R2E4N8B ~/GitHub/pagaten
$ git push https://<ACCESS TOKEN>@github.com/ib-m-j/pagaten
Counting objects: 3, done.
Delta compression using up to 2 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 302 bytes | 60.00 KiB/s, done.
Total 3 (delta 2), reused 0 (delta 0)
remote: Resolving deltas: 100% (2/2), completed with 2 local objects.
To https://github.com/ib-m-j/pagaten
2dc4f9f..c0c7e2c master -> master
Ib@DESKTOP-R2E4N8B ~/GitHub/pagaten
$ git status
On branch master
Your branch is ahead of 'origin/master' by 1 commit.
(use "git push" to publish your local commits)
nothing to commit, working tree clean