Tutorial does not indicate that you need to fork the repository before you clone it, otherwise the push command fails with an authentication error

[meg2415]

I followed the steps in the video tutorial and when I got to the "push" step, I got a 403 error. I then looked a the README file and saw that step #3 says to fork the repository, though the video tutorial does not mention that step.

[frogking702]

$ git push origin update-name
remote: Permission to LadyKerr/GitGoing.git denied to frogking702.
fatal: unable to access 'https://github.com/LadyKerr/GitGoing.git/': The requested URL returned error: 403

[frogking702]

Yes, i encountered the same problem error 403. I also use the fork to the repository to solve this.

Here’s a clean step-by-step record of how you solved the 403 issue, used a fork, and got set up to create a PR successfully.

Identify the cause of the 403

Error: Permission to LadyKerr/GitGoing.git denied to frogking702 (403)

Meaning: you were trying to push to the upstream repo (LadyKerr/GitGoing) without write permission.

Create your own fork on GitHub

Opened the upstream repo page: LadyKerr/GitGoing

Clicked “Fork”

Selected your account: frogking702

Result: your fork repo exists at frogking702/GitGoing

Point your local repo to your fork (origin)

Checked remotes:

git remote -v

Ensured origin points to your fork:

origin https://github.com/frogking702/GitGoing.git

If it was still pointing to LadyKerr, you would fix it with:

git remote set-url origin https://github.com/frogking702/GitGoing.git

Add the upstream remote (so you can pull updates from the original repo)

Added upstream:

git remote add upstream https://github.com/LadyKerr/GitGoing.git

Verified remotes again:

git remote -v

Your final correct remote configuration (what you already have now):

origin = your fork (read/write)

upstream = original repo (read-only for you)

Push your working branch to your fork (fixes 403 permanently)

Worked on branch: update-name

Pushed to your fork:

git push -u origin update-name

Result: the branch exists on your fork, not the upstream repo, so no permission error.

Create a Pull Request back to the upstream repo

Opened your fork page: https://github.com/frogking702/GitGoing

Used “Compare & pull request”, or went to “Pull requests” → “New pull request”

Base repository: LadyKerr/GitGoing (main/master)

Compare repository: frogking702/GitGoing (update-name)

Clicked “Create pull request”

Optional “one-link” method to create PR directly:

If upstream base branch is main:

main...frogking702:update-name

If upstream base branch is master:

master...frogking702:update-name

If you want, paste the output of git log --oneline -3 and I can help you write a concise PR title + description that matches what you changed.

[JaggedBishop]

Yes, i encountered the same problem error 403. I also use the fork to the repository to solve this.

Here’s a clean step-by-step record of how you solved the 403 issue, used a fork, and got set up to create a PR successfully.

Identify the cause of the 403

Error: Permission to LadyKerr/GitGoing.git denied to frogking702 (403)

Meaning: you were trying to push to the upstream repo (LadyKerr/GitGoing) without write permission.

Create your own fork on GitHub

Opened the upstream repo page: LadyKerr/GitGoing

Clicked “Fork”

Selected your account: frogking702

Result: your fork repo exists at frogking702/GitGoing

Point your local repo to your fork (origin)

Checked remotes:

git remote -v

Ensured origin points to your fork:

origin https://github.com/frogking702/GitGoing.git

If it was still pointing to LadyKerr, you would fix it with:

git remote set-url origin https://github.com/frogking702/GitGoing.git

Add the upstream remote (so you can pull updates from the original repo)

Added upstream:

git remote add upstream https://github.com/LadyKerr/GitGoing.git

Verified remotes again:

git remote -v

Your final correct remote configuration (what you already have now):

origin = your fork (read/write)

upstream = original repo (read-only for you)

Push your working branch to your fork (fixes 403 permanently)

Worked on branch: update-name

Pushed to your fork:

git push -u origin update-name

Result: the branch exists on your fork, not the upstream repo, so no permission error.

Create a Pull Request back to the upstream repo

Opened your fork page: https://github.com/frogking702/GitGoing

Used “Compare & pull request”, or went to “Pull requests” → “New pull request”

Base repository: LadyKerr/GitGoing (main/master)

Compare repository: frogking702/GitGoing (update-name)

Clicked “Create pull request”

Optional “one-link” method to create PR directly:

If upstream base branch is main:

main...frogking702:update-name

If upstream base branch is master:

master...frogking702:update-name

If you want, paste the output of git log --oneline -3 and I can help you write a concise PR title + description that matches what you changed.

Thank you! This works.