Shouldn't isVersionBump be judged by the last commit? about gh-action-bump-version

[phips28]

Its intended to look into all commit messages.

We could introduce a config flag like ciCheckInLastMessageOnly Or any better naming 😉

if you want to create a PR I can merge it

[ghm-salvarado]

Similar issue here, but related to a PR that was squashed and merged:

messages: [
  'pull request title\n' +
    '\n' +
    '* squashed commit message\r\n' +
    '\r\n' +
    '* ci: version bump to v0.32.0\r\n' +
    '\r\n' +
    '* squashed commit message\r\n' +
    '\r\n' +
    '* squashed commit message\n' +
    'undefined'
]
✔  success   No action necessary!

There's only one string in the messages array, but since ci: was present in the body of a commit from an upstream merge into this branch, the workflow was skipped. Would it make sense to add a ^ to the regex to ensure only ci: in the very beginning of the message triggers a skip?

[phips28]

@ghm-salvarado if you want to create a PR I can merge it

[dallen4]

Just curious about the status of this issue or if anyone is working on a patch? I implement this version bump in multiple branches (deployment stages) and when merging into production branch it doesn't bump out of the pre-release version because it detects the older bumps. Will work on a flag or something to implement if this isn't being worked on 🙂

[phips28]

afaik no one worked on this. So happy to merge your PR.

[dallen4]

I took it a step further to allow for a couple settings. See #146.

[phips28]

thanks! :)