-
Notifications
You must be signed in to change notification settings - Fork 10
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
New project creation fails when pushing to GitHub, but repo created succesfully #751
Comments
Interestingly, when looking at the remote, it looks like there is a space that introduced itself before the PAT:
I suppose that when I pasted the PAT while doing Question: should |
After manually changing the remote's URL to remove the space, a manual I will now delete the repo, update the config to have the space removed from the PAT, and hopefully confirm that the rest of the process works. |
SUCCESS (at last, after the 3 issues listed above and this one ;) ) The question at the bottom of this post is thus to be discussed, why did the PAT with the space get accepted to created the repository, but not to push, and should there be some basic check/sanitation be made on the PAT when doing |
@Imipenem would you be willing to hack some PAT validations? Should be very easy. @e2jk perfectly agree. This should be validated. |
* Fix #751: Basic PAT validation + CI fix * PR feedback Signed-off-by: zethson <[email protected]> Co-authored-by: zethson <[email protected]>
[EDIT] this issue was caused by a space at the beginning of my GitHub PAT. reconfiguring works. Nonetheless, see this post with a question about improving the user experience
Associated Template/Command/Core
After navigating around these 3 issues #748, #749 and 750, I'm facing yet another "interesting" situation.
I have created a personal access token on GitHub giving it these access rights:
(you see that when selecting "workflow", all previous options under "repo" are automatically selected, guaranteeing that these rights are available to my PAT...)
When creating a new project, the empty repository is nicely created on GitHub, but for some reason the
git push
command gets blocked?Is there another option I should give to my personal access token? Normally pushing to the repo is handled by the "repo" group...
Describe the bug
To Reproduce
Steps to reproduce the behavior:
create
Full `--verbose` output of the command (Click to expand)
Expected behavior
I would have expected the
git push
command to succeed, since the repo has been created succesfully.System:
pipx
)pipx
Additional context
Please ask if any other detail would be needed. In the meantime I'll start with the files created in the folder, and will handle the project creation manually on GitHub.
The text was updated successfully, but these errors were encountered: