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
So I recently came across an issue where my commit message couldn't actually include "branch.name".
Upon further investigation, I found this section of the prepare code:
git/lib/prepare.js
Line 65 in 09200b1
await commit( message ? template(message)({branch: branch.name, lastRelease, nextRelease}) : `chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}`, {env, cwd} );
It looks like we've historically been adding branch as just the branch name. Before I submit a PR, it seems there are two ways that this can go:
I wanted to report this as an issue before trying to submit a PR that makes the opinion.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
So I recently came across an issue where my commit message couldn't actually include "branch.name".
Upon further investigation, I found this section of the prepare code:
git/lib/prepare.js
Line 65 in 09200b1
It looks like we've historically been adding branch as just the branch name. Before I submit a PR, it seems there are two ways that this can go:
I wanted to report this as an issue before trying to submit a PR that makes the opinion.
The text was updated successfully, but these errors were encountered: