Ignore bots signoff check

[dolby360]

in case a branch contains bot commits then these commits will not be checked.
this code assumes that the email address of all bots contains [bot].

Signed-off-by: dolby360 [email protected]

Pull Request

Description

Describe what you did and why.

Related issue (if any): fixes #47

Checklist

• [V] I have followed this repository's contributing guidelines.
• [V] I have used the conventional commits specification for my commit messages.
• [V] I have signed my commits.
• [V] I will adhere to the project's code of conduct.

Additional information

Anything else?

[TomerFi]

@dolby360
We have 3 typos failing test, and the CI workflows:

---

here:

.withArgs(fakeUnknownEmail, sinon.match.func)

change fakeUnknownEmail to fakeBotEmail.

---

here:

listCommitsStub.resolves({data: [commitSignedByUnknown]});

change commitSignedByUnknown to commitUnsignedBot.

---

the commit message type is feat!, amend it to feat.

[TomerFi]

@dolby360
Thank you very much, I will be merging this by tomorrow.

I just want to take the opportunity of this PR and fix the CI issue,
the "Report test results" step fails because of missing permission for forks,
and I can verify a fix with your PR open, so I want to play with it a bit if you don't mind.

Can you please verify the Allow edits by maintainers. checkbox is ticked so I can push a fix here?

[dolby360]

Can you please verify the Allow edits by maintainers. checkbox is ticked so I can push a fix here?

Already on. Please take your time there's no rush.

[TomerFi]

Already on. Please take your time there's no rush.

Weird... I try pushing yesterday, and I got a permissions error, I figured it's the maintainers' thing, but I didn't look anymore into it.

I am looking into it now.

EDIT:
It was some lfs issue on my end, pushed successfully.
thanks!

EDIT 2:
In regards to the failed CI, turns out it's a known issue and it looks like it's going to be resolved soon.
dorny/test-reporter#168