-
Notifications
You must be signed in to change notification settings - Fork 407
create_pull documentation is insufficient and incorrect #259
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
Comments
Feel free to create a PR |
I had considered doing so, but didn't have the time to understand your On 23 June 2014 22:05, Ian Cordasco notifications@github.com wrote:
|
The tests and the docs are separate entities. They do not affect each other. Simply fixing the docs does not require understanding of the tests. |
Sure, but the tests are not sufficient. Fine. I'll fix only the docs. On 24 June 2014 09:15, Ian Cordasco notifications@github.com wrote:
|
It would also be nice to make On 24 June 2014 09:32, Joel Nothman jnothman@student.usyd.edu.au wrote:
|
For future readers who find this and realize I never responded to @jnothman's last idea, here's the problem: while most repositories use |
But you could still make |
So I try to mirror the GitHub API. If something is required by the API, I require it be provided by the user. That said, I could allow the user to pass |
I agree. Github requires it, we should enforce that requirement. |
github3.py/github3/repos/repo.py
Line 710 in b4a2783
username:branch
. This is incorrect.create_pull
should be called on the base repository (this should be documented), in which case the username (project, really) is predetermined.base
should be merely the branch (usuallymaster
).head
should beusername:branch
.The text was updated successfully, but these errors were encountered: