[bug] somehow it detects commits that i have since force-pushed myself away from

[C0DK]

in my repo i had a bad commit, so i renamed it and force pushed in my PR however the check still fails somehow, and shows the old message. It seems it catches something in the wrong way.

On top of this, if i let this run on my master branch, it will fail on my newest commit because i have a really old commit that doesn't conform the my naming convetion, rather than only checking the commit at hand. should i use another regex flag? (for thsi reason i disabled the check on anything but pull requests)

name: "Commit Message Check"
on:
  pull_request:
    types:
      - opened
      - edited
      - reopened
      - synchronize

jobs:
  check-commit-message:
    name: Check Commit Message
    runs-on: ubuntu-latest
    steps:
      - name: Check Commit Type
        uses: gsactions/commit-message-checker@v1
        with:
          pattern: '(ID-\d+|FIX): .+'
          flags: "gm"
          error: "Naming convention is `[ID]: [summary]` i.e `ID-404: Fixed My Shit`"

[C0DK]

i had to delete my PR and create it again - that fixed it :)

[gilbertsoft]

Thanks for your report. Not sure what was wrong. But is there an action required or can we close this issue?

[C0DK]

The bug still exists, however by deleting the PR your script seems to lose access to prior versions. I ended up not using your action due to a lot of bugs with the commit checked.
In PRs it checks all commits, also commits that no longer exists (i.e if you force push a new history)
and in the general backlog it checks all prior commits when checking a given commit, not just the commit in question, which is problematic.

[gilbertsoft]

Probably it's related to your pull request types, I never used types so far. I will have a look if I can somehow include this cases to my tests.

[gilbertsoft]

@C0DK Just released a new version which probably also solves your issue. If not please send me a link to your failing action and/or repository for a deeper investigation. Thx