-
-
Notifications
You must be signed in to change notification settings - Fork 13
Always seems to be missing one commit. #36
Comments
This comment has been minimized.
This comment has been minimized.
I'm not sure of what's happening, the tests work correctly:
I wonder if the merge commit in your diff is throwing the count off somehow |
Perhaps... I’ll try some more testing today perhaps with a few more than just two commits. |
Something is definitely wrong. I just tried this command on this repo and it reports something unexpected:
This doesn't match GitHub’s diff, which only has 5 commits: v3.1.0...v3.2.0 cc @notlmn |
When I clone this repository and run ❯ git log --format=%H¬%ad¬%s --date=short v3.1.0..v3.2.0
f047902b085bbb7ffae3ecd36d73842b76355dad¬2021-02-22¬Add support for `{date}` replacement (#33)
6e89f5c9d6622f54ca284c06aa89fa7391cd86f7¬2021-02-04¬Update user in examples
5c804153ef8227047cf9bf373a704791aa3ee755¬2020-12-30¬Bump node-notifier from 8.0.0 to 8.0.1 (#26)
524027dd065f8486af7919212e355aa5523bebbd¬2020-12-30¬Bump ini from 1.3.5 to 1.3.8 (#24)
a170b2e671cf2763b5060b4e4747401181929635¬2020-10-23¬Fix minor typo in readme headings |
I get the same output as @BelKed. |
Also, when I run ❯ git log --format=%H¬%ad¬%s --date=short v0.3.0..v0.3.1
bb5441d8617c586d3a676e49b1113743210666a2¬2021-02-24¬chore(release): Automated version bumping to v0.3.1
4fcb30dcc5eab68717260ea49f216bd198e3337c¬2021-02-24¬Merge branch 'master' of github.com:fredbradley/actions-test
4cf6469146d04e314f59d516d73e8cded2e66150¬2021-02-24¬testing out something else |
Is it to do with the additional use of I've just added a v0.6.0 with many more commits, and no 'Merge' commit messages. But the changelog is still only show two commits. |
Try running just |
In https://github.com/fredbradley/actions-test/releases/tag/v0.7.0 I've removed the other @stefanzweifel action, and now the changelog shows all commits as expected. So I guess I need to work out what it is with the other action that is suppressing it all. I've a feeling it's to do with the |
I think, that is caused by creating a commit in action. You maybe have to fetch second time before creating a release to get all commits using |
Unfortunately the output of GitHub Actions matches mine. Check out the CI log of this failing commit: ff23290 |
Hello I’ve been testing this today however it seems that each time it misses the first commit of the group.
Crude example can be found: https://github.com/fredbradley/actions-test/releases/tag/v0.3.1
but when you see the compare you see it’s three commits not two.
The text was updated successfully, but these errors were encountered: