Error 403 #203860
Replies: 2 comments 1 reply
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
this isn’t related to the repo being public or private. The commit is failing locally before Git even reaches GitHub. The main error is: Basically, GPG is trying to ask for your key’s passphrase, but the VS Code container can’t open the prompt properly. Also, creating multiple keys won’t really fix it, especially if the private key was created outside the container and isn’t available inside it. If you don’t actually need signed commits, the easiest fix is: git config --local commit.gpgsign false
git commit -m "deleted settings.json"
git pushIf you do need commit signing, try this inside the VS Code terminal: export GPG_TTY=$(tty)
echo 'export GPG_TTY=$(tty)' >> ~/.bashrcThen check which secret keys are actually available inside the container gpg --list-secret-keys --keyid-format=longUse one of those keys: git config --global user.signingkey YOUR_KEY_ID
git config --global gpg.program gpgRestart the terminal and try committing again. Also, the reason |

this isn’t related to the repo being public or private. The commit is failing locally before Git even reaches GitHub.
The main error is:
Basically, GPG is trying to ask for your key’s passphrase, but the VS Code container can’t open the prompt properly.
Also, creating multiple keys won’t really fix it, especially if the private key was created outside the container and isn’t available inside it.
If you don’t actually need signed commits, the easiest fix is:
If you do need commit signing, try this inside the VS Code terminal: