-
Notifications
You must be signed in to change notification settings - Fork 186
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
Issue with setup (GithubException.GithubException: 422) #293
Closed
Nolanrulesroblox opened this issue
Sep 2, 2020
· 2 comments
· Fixed by #296 or codepaws/statuspage#1
Closed
Issue with setup (GithubException.GithubException: 422) #293
Nolanrulesroblox opened this issue
Sep 2, 2020
· 2 comments
· Fixed by #296 or codepaws/statuspage#1
Comments
Got the same issue, found out how it works? |
pasuder
added a commit
to pasuder/statuspage
that referenced
this issue
Oct 16, 2020
As per PyGithub#1210 slash at beginning of path cannot be used. Fix: jayfk#293
pasuder
added a commit
to pasuder/statuspage
that referenced
this issue
Oct 16, 2020
bongo is us2 |
chenrui333
pushed a commit
that referenced
this issue
Feb 23, 2022
* Remove slash from path As per PyGithub#1210 slash at beginning of path cannot be used. Fix: #293 * Replace master with main Due to GitHub branch naming convention, starting from 1st October, all new repositories are having main instead of master branch. * Use get_contents instead of get_file_contents Due to PyGithub#1222 and PyGithub#1223 * update_file cannot use slash Fix #293
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here is the error given:
github.GithubException.GithubException: 422 {"documentation_url": "https://docs.github.com/rest/reference/repos#create-or-update-file-contents", "message": "path cannot start with a slash", "errors": [{"field": "path", "code": "invalid", "resource": "Commit"}]}
The API key is fully setup
The text was updated successfully, but these errors were encountered: