This repository was archived by the owner on Sep 11, 2020. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A few issues have been reported recently (#481 and #430) that relate to some API confusion around creating new references for a repository.
I'm curious if there is some benefit to providing some high level API in Repository to enable the creation of branches and/or tags.
I threw together this patch to gather some quick feedback on whether this is something beneficial for the project, and to see if the API makes sense. I started with
CreateBranch
for now. Tests, further documentation, and demo examples are pending.I figured that sticking to the options pattern for the arguments to CreateBranch would give us the ability to extend this easily in the future to support other features available in the standard
git branch
tool. Such features include configuring an upstream branches, tracking branches, editing description, etc.