Checkout testcases

[hhsecond]

Description

Test cases & name validity check for the branch name

Types of changes

• 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)

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 added tests to cover my changes.
• All new and existing tests passed.

[hhsecond]

@rlizzo I would like to hear your thoughts in a couple of cases and hence keeping it incomplete. Would be great if you can review the #TODOs and we can take it from there

[rlizzo]

In general, these are fairly well thought out tests for the basics of working with checkout and merge commits. A few comments are left below, but nothing major aside from one or two of the (potential) bugs you've found (nice job catching them btw!)

Nice work sherin, much appreciated!

[rlizzo]

So I'm a bit confused as to the status of this? I think there's a lot of overlap with #32, and this branch doesn't seem like it's really kept up with the changes in master.

Do you want to continue with this PR? Or include the relevant changes in #32 along with a most focused commit for the remainder?

[hhsecond]

The TODOs in this PR is not just related to #32. There are few other changes that we haven't looked into at all. So I would say, let's merge this and then along with rebasing #32, will sort out what's required there. Once #32 lands, we'll have a stable master on which I can do a clean up perhaps.

[rlizzo]

Ok sounds good. I'm just going to rerun the tests to make sure everything is OK, then will merge this and rebase #32.