Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BRANCHES AREN'T JUST FOR BIRDS #49015

Open
loewen-behold opened this issue May 4, 2023 · 1 comment
Open

BRANCHES AREN'T JUST FOR BIRDS #49015

loewen-behold opened this issue May 4, 2023 · 1 comment

Comments

@loewen-behold
Copy link
Contributor

@jlord
I've tried to look into the previous issue submissions with the same issue, but was unable to troubleshoot successfully.

I am unable to push my changes on my created branch (as per what I understood of the instructions). I've checked the sources for the remotes, and they appear to be as they should, yet I continue to receive the same error that I am unable to access this path.

Here's a sample of my "remote -v" output and what error message i get when I try to push:

(base) MacBook-iLo:patchwork jlo$ git remote -v
origin https://github.com/loewen-behold/patchwork.git (fetch)
origin https://github.com/loewen-behold/patchwork.git (push)
upstream https://github.com/jlord/patchwork.git (fetch)
upstream https://github.com/jlord/patchwork.git (push)
(base) MacBook-iLo:patchwork jlo$ git push origin add-loewen-behold
remote: Permission to loewen-behold/patchwork.git denied to loewen-behold.
fatal: unable to access 'https://github.com/loewen-behold/patchwork.git/': The requested URL returned error: 403"

@loewen-behold
Copy link
Contributor Author

loewen-behold commented May 4, 2023

Update: Although my account is an administrative account, I had to login as root (sudo) user for the push command to work for me.
I also had to generate a personal access token for the repo since the push command was followed by a login prompt to github asking for username and pass (used the generated code for pass)

I don't really feel comfortable having to do this every time, so a better fix would be appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant