We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using git-create-pr for a branch containing several commits, such as:
git-create-pr
$ git log master.. --format=oneline b21a579208e743dcc57f70e8492a8555d38ed61c (HEAD -> release-0.7.0a1, origin/release-0.7.0a1) release: 0.7.0a1 e1ce41ce85840a4c7cd56e581dccf4d59f36709b pip-compile upgrade of dependencies 27c6df46f9b0a8bc051c971cb412473e6a23ce9c installation: bump shared modules
the git-create-pr command created this PR:
i.e. the oldest commit is visible as the PR name.
It would be better to use the latest commit as the most significant and better populate the PR body with oneliners for each commit.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When using
git-create-pr
for a branch containing several commits, such as:the
git-create-pr
command created this PR:i.e. the oldest commit is visible as the PR name.
It would be better to use the latest commit as the most significant and better populate the PR body with oneliners for each commit.
The text was updated successfully, but these errors were encountered: