-
Notifications
You must be signed in to change notification settings - Fork 365
Commit
Branch.cherry_pick()
(#7348)
* Implement `Branch.cherry_pick()` As a minimal wrapper around `BranchesApi.cherry_pick()`. Since the API returns the created commit , we return the corresponding SDK wrapper model constructed directly from the API response. Adds an integration test cherry-picking a commit onto main, checking metadata and message equality. * Tweak parent_number description in cherry-pick API and Python docstring * Add `force` option to `Branch.cherry_pick()` In line with the cherry pick API, currently a no-op. * Revert "Add `force` option to `Branch.cherry_pick()`" This reverts commit fbe4027. * Add line break to parent_number docstring to satisfy pylint * fix generated docs * fix generated docs 2 * fix generated docs 3 --------- Co-authored-by: Nir Ozery <[email protected]>
- Loading branch information
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.