Skip to content

Conversation

lucastoro
Copy link
Contributor

git bc-show-eligible BRANCH parameter is now optional, defaults to 'master'.
git bc-show-eligible can be called from repo's subfolders.

…aster'.

Now git bc-show-eligible can be called from repo's subfolders.
parser = argparse.ArgumentParser(description='Show commits, eligible for cherry-picking')
parser.add_argument('branch', metavar='BRANCH', help='Name for the branch to check against')
parser.add_argument('branch', metavar='BRANCH', help='Name for the branch to check against',
default='master', nargs='?')
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think origin/master is better. In case you are on a release branch, you do git pull and check the eligible commits. Many times master and origin/master are misaligned, and the latter seems to be a safer default.


args = parser.parse_args()
repo = pygit2.Repository('.')
repo = pygit2.Repository(top)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is very welcome indeed

@mbrt mbrt merged commit 4a029d6 into Bright-Computing:master Jul 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants