-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
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
feat!: support multiple commits in footer #686
Conversation
Codecov Report
@@ Coverage Diff @@
## master #686 +/- ##
==========================================
+ Coverage 85.04% 85.15% +0.10%
==========================================
Files 48 48
Lines 5838 5894 +56
Branches 542 520 -22
==========================================
+ Hits 4965 5019 +54
- Misses 872 874 +2
Partials 1 1
Continue to review full report at Codecov.
|
(node: FooterNodes) => { | ||
switch (node.type) { | ||
case 'scope': | ||
footerText += `(${node.value})`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is necessary because we don't currently include (
and )
in the parser, I'd like to add a parenthesis
node, which would simplify logic.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the meta:
header required to parse the extra commit messages?
If not, I could see inadvertent messages being parsed from a multiple commit squash and merge from the GitHub UI.
src/conventional-commits.ts
Outdated
@@ -71,6 +71,30 @@ interface Note { | |||
text: string; | |||
} | |||
|
|||
function getParsedCommits(commits: Commit[]) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add the return type?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update the README to describe what you can do with this feature.
🤖 I have created a release \*beep\* \*boop\* --- ## [9.0.0](https://github.com/googleapis/release-please/compare/v8.2.0...v9.0.0) (2021-01-08) ### ⚠ BREAKING CHANGES * support multiple commits in footer (#686) ### Features * support multiple commits in footer ([#686](https://github.com/googleapis/release-please/issues/686)) ([b3f96d8](https://github.com/googleapis/release-please/commit/b3f96d8dd988b7d482223e8a7868a45043db4880)) ### Bug Fixes * `findFilesByfilename` respects `path` option ([#665](https://github.com/googleapis/release-please/issues/665)) ([a3a1df6](https://github.com/googleapis/release-please/commit/a3a1df690f48b38c539ee5aab5ae046d640c6811)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please).
BREAKING CHANGE: footers that look like commits will now be displayed in the CHANGELOG.
This PR adds support for expanding multiple commits, represented by a single commit message, into multiple commits in the CHANGELOG.
It expects the format:
Where:
meta: multiple commits
, can be anything), there are footers that looks like Conventional Commits.Refs: #667
Fixes: #614
CC: @miraleung