Commit809e2fd

committed

pull requests should be created between branches

1 parent120b716 commit809e2fdCopy full SHA for 809e2fd

File tree

-5

lines changed

-5

lines changed

Lines changed: 2 additions & 5 deletions

Original file line number	Diff line number	Diff line change
`@@ -80,14 +80,11 @@ Pass the appropriate [media type](/v3/media/#commits-commit-comparison-and-pull-`
`80`	`80`	`Name \| Type \| Description`
`81`	`81`	`-----\|------\|-------------`
`82`	`82`	`title`\|`string` \|Required. The title of the pull request.
`83`		-`head`\|`string` \|Required. Thebranch (or git ref) where your changes are implemented.
`84`		-`base`\|`string` \|Required. Thebranch (or git ref) you want your changes pulled into. This should be an existing branch on the current repository. You cannot submit a pull request to one repository that requests a merge to a base of another repository.
	`83`	+`head`\|`string` \|Required. Thename of the branch where your changes are implemented. For cross-repository pull requests in the same network, namespace`head` with a user like this:`username:branch`.
	`84`	+`base`\|`string` \|Required. Thename of the branch you want your changes pulled into. This should be an existing branch on the current repository. You cannot submit a pull request to one repository that requests a merge to a base of another repository.
`85`	`85`	`body`\|`string` \| The contents of the pull request.
`86`	`86`
`87`	`87`
`88`		-NOTE:`head` and`base` can be either a sha or a branch name. Typically you
`89`		-would namespace`head` with a user like this:`username:branch`.
`90`		`-`
`91`	`88`	`####Example`
`92`	`89`
`93`	`90`	`<%= json\`

Comments

(0)