Branch Deletion

[rlizzo]

Motivation and Context

Why is this change required? What problem does it solve?:

Allow for the ability to remove the pointers to local branches.

If it fixes an open issue, please link to the issue here:

• will close Branch removal #38

Description

Describe your changes in detail:

See Repository.remove_branch() docstrings for overview of utility & considerations taken.

The create_branch() method was updated to return same results as remove_branch() (now yielding both the subject branchs` name as well as its referent commit digest). Appropriate modifications were made to the test suite to adapt to (and test) this behavior, and the "branch modification" methods were given their own test module for future clarity as we expand on their abilities.

I am currently working on adding analagous methods to the CLI, and will push those before this is merged.

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

• Documentation update
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Is this PR ready for review, or a work in progress?

• Ready for review
• Work in progress

How Has This Been Tested?

Put an x in the boxes that apply:

• Current tests cover modifications made
• New tests have been added to the test suite
• Modifications were made to existing tests to support these changes
• Tests may be needed, but they are not included when the PR was proposed
• I don't know. Help!

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have signed (or will sign when prompted) the tensorwork CLA.
• I have added tests to cover my changes.
• All new and existing tests passed.

@hhsecond, let me know what you think.

[hhsecond]

LGTM

[codecov]

Codecov Report

Merging #128 into master will increase coverage by 0.28%.
The diff coverage is 98.21%.

@@            Coverage Diff             @@
##           master     #128      +/-   ##
==========================================
+ Coverage    92.1%   92.37%   +0.28%     
==========================================
  Files          60       61       +1     
  Lines       10087    10333     +246     
  Branches      999     1007       +8     
==========================================
+ Hits         9290     9545     +255     
+ Misses        582      572      -10     
- Partials      215      216       +1

Impacted Files	Coverage Δ
src/hangar/records/parsing.py	98.51% <ø> (ø)	⬆️
src/hangar/records/summarize.py	90.41% <ø> (ø)	⬆️
src/hangar/records/queries.py	91.88% <ø> (ø)	⬆️
src/hangar/records/commiting.py	89.92% <ø> (ø)	⬆️
tests/test_cli.py	100% <100%> (ø)	⬆️
tests/test_remotes.py	98.42% <100%> (ø)	⬆️
src/hangar/records/heads.py	93.07% <100%> (+6.27%)	⬆️
tests/test_visualizations.py	100% <100%> (ø)	⬆️
src/hangar/repository.py	96.75% <100%> (+0.11%)	⬆️
src/hangar/utils.py	84.35% <100%> (+1.36%)	⬆️
... and 5 more