Unable to git push project created in Codespaces

[valhuber]

I have a project working well in codespaces. It runs, and I am able to push changes to my repo, so my git credentials appear to be working for that project.

But if I try to create a new project, I am unable to git push origin master it - getting

      remote: Permission to PoseyDev/MyProject.git denied to PoseyDev.
      fatal: unable to access 'https://github.com/PoseyDev/MyProject.git/': The requested URL returned error: 403

I have documented the exact commands and responses here. I am a naive git user, so this could well be a cockpit error.

[jdevfullstack]

is this your another account ?

that might be a confusion because you are using two accounts

[valhuber]

It is the account for both. The first project was a fork, if that matters…

On Sat, Jul 30, 2022 at 10:21 PM jdevstatic ***@***.***> wrote: is this your another account ? [image: image] <https://user-images.githubusercontent.com/47092464/182011408-ad5e6a23-1617-48e4-889c-ba395249f5f1.png> that might be a confusion because you are using two accounts — Reply to this email directly, view it on GitHub <#27769 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKSG36J5BKPRP6J5MRK7X3VWYEONANCNFSM55EIZRDQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Thanks, Val 510-703-5909 valhuber on skype

[jdevfullstack]

It is the account for both.

what do you mean by that ? I tried testing it in the past, using two accounts, the problem is that, if it's on the same machine, all of the commits will be mixed by the other account, which is actually a mess,

[valhuber]

I have my wife’s account PoseyDev for testing “not me”. It’s the only account I was using for exercise. I am doing it from her machine, so there is no mixing of accounts as far as I know.

…

On Jul 30, 2022, at 10:41 PM, jdevstatic ***@***.***> wrote: It is the account for both. what do you mean by that ? I tried testing it in the past, using two accounts, the problem is that, if it's on the same machine, all of the commits will be mixed by the other account, which is actually a mess, — Reply to this email directly, view it on GitHub <#27769 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKSG3ZSJJNYY4OACZ4CYX3VWYG2BANCNFSM55EIZRDQ>. You are receiving this because you authored the thread.

[jdevfullstack]

do you use the same computer ? that's what happened to me, even if just once

[valhuber]

Hi...

Appreciate your time here... I have re-run my test, eliminating the "other" github account. Now it's all under my account (valhuber). The problem still occurs as documented here.

[jshorty]

👋 Hello from the Codespaces team! This is expected behavior at the moment, so not a cockpit error 😄. By default the token your codespace uses to authenticate requests to GitHub is scoped only to repository that it's created with— and so will be forbidden to write to the remote you've set up for your newer repository from within the codespace.

Here is the recommended path for expanding the permissions of a codespace to include other repositories:
https://docs.github.com/en/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces

This flips the steps you've documented around, however— it would require you to set up the remote GitHub repo before spinning up the other codespace. We'd be curious to hear if this is a source of friction for you.

You may also find this blog post relevant! https://github.blog/2022-04-20-codespaces-multi-repository-monorepo-scenarios/

[anaisbetts]

This decision basically makes Codespaces effectively useless for contributing to Open Source:

1. Create Codespace of upstream repo
2. Make PR
3. Create fork of repo so that you can publish changes
4. You cannot push your changes anywhere - the upstream repo is read-only, and your token has no access to the fork. You now cannot push anywhere and your changes are stuck on the Codespace. I had to move them by copy-pasting diffs.

[ozyman42]

this seems incompatible with git submodules.

[ozyman42]

Here's how to solve it in case recreating the codespace is not an option
https://docs.github.com/en/codespaces/troubleshooting/troubleshooting-authentication-to-a-repository#authenticating-to-repositories-that-you-didnt-create-the-codespace-from

[sarath49]

Step 5 does not work, so does that mean to follow the instructions smoothly, need me to be Microsoft employee?
https://github.com/skills/code-with-codespaces/blob/main/.github/steps/1-first-codespace.md

[sarath49]

Now it works, it looks like we have to wait for few minutes before the push start working, earlier it was all about "remote: Invalid username or password."

[valhuber]

Good information, and will surely ponder. Glad it was not a cockpit error!

…

On Aug 2, 2022, at 12:08 PM, Jake Shorty ***@***.***> wrote: 👋 Hello from the Codespaces team! This is expected behavior at the moment, so not a cockpit error 😄. By default the token your codespace uses to authenticate requests to GitHub is scoped only to repository that it's created with— and so will be forbidden to write to the remote you've set up for your newer repository from within the codespace. Here is the recommended path for expanding the permissions of a codespace to include other repositories: https://docs.github.com/en/codespaces/managing-your-codespaces/managing-repository-access-for-your-codespaces This flips the steps you've documented around, however— it would require you to set up the remote GitHub repo before spinning up the other codespace. We'd be curious to hear if this is a source of friction for you. You may also find this blog post relevant! https://github.blog/2022-04-20-codespaces-multi-repository-monorepo-scenarios/ — Reply to this email directly, view it on GitHub <#27769 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKSG37EN7WRAML7X3HAHT3VXFW2FANCNFSM55EIZRDQ>. You are receiving this because you authored the thread.

[valhuber]

I checked her computer, I don’t see my git account. But this is in codespaces, so that’s a different world, no? But you made me wonder… did this ***@***.***:/workspaces/Tutorial-ApiLogicProject$ git config --list credential.helper=/.codespaces/bin/gitcredential_github.sh user.name=PoseyDev ***@***.*** gpg.program=/.codespaces/bin/gh-gpgsign core.repositoryformatversion=0 core.filemode=true core.bare=false core.logallrefupdates=true remote.upstream.url=https://github.com/valhuber/Tutorial-ApiLogicProject remote.upstream.fetch=+refs/heads/*:refs/remotes/upstream/* branch.main.remote=origin branch.main.merge=refs/heads/main remote.origin.url=https://github.com/PoseyDev/Tutorial-ApiLogicProject.git remote.origin.fetch=+refs/heads/*:refs/remotes/origin/* ***@***.***:/workspaces/Tutorial-ApiLogicProject$ Remember, this all started from forking the project in red, which is in fact my git account. Do you think that might be the culprit? Thanks, Val

…

On Jul 31, 2022, at 7:34 AM, jdevstatic ***@***.***> wrote: do you use the same computer ? that's what happened to me, even if just once — Reply to this email directly, view it on GitHub <#27769 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABKSG32CB7TS7RJBNWG53ZLVW2FHNANCNFSM55EIZRDQ>. You are receiving this because you authored the thread.