docs: add vidavidorra/commitlint-plugin-function-rules project

[jdbruijn]

Plugin to use functions as rule value.

Description

Add commitlint plugin function rules as community project.

@escapedcat As per your suggestion in #1698 (comment). I've kept it in the same style as the commitlint.io project.

Motivation and Context

Add my project.

Usage examples

n/a

How Has This Been Tested?

n/a

Types of changes

Not actually a bug fix but docs update, so I guess this type 😉

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[escapedcat]

Looks good I think. Later on we could give plugins their own section or deal with it differently.

I just don't have a clue why - only on your PRs - the checks always look this:

You have any idea? It's the same on your types-PR.

[jdbruijn]

You have any idea?

I honestly have no idea. I indeed noticed the same on my other PR, but thought nothing about it at that time. I've just forked this repo, made my changes, pushed them and then created a PR here. I do the same steps for other projects and haven't run into any issues there. I even checked whether there were any branch protection rules on my fork, but there aren't, not that I think that should make any difference.

[escapedcat]

Haha, yeah, it's weird.
@byCedric any idea?

[jdbruijn]

I obviously can't see the settings, but found these topics on the issue.

• https://github.community/t/expected-waiting-for-status-to-be-reported/16727/2
• https://github.community/t/expected-waiting-for-status-to-be-reported/18001/6
• https://stackoverflow.com/questions/52200096/github-pull-request-waiting-for-status-to-be-reported

I also have the WIP GitHub app installed on my side on all repositories, also doubt that would be an issue, but I've disabled that for now to check. I'll also try to push a new commit to try and trigger the checks. I did check the branch naming, but doubt that is it as other PR's use similar naming, e.g. ellsclytn:feat/help-url-in-config.

[jdbruijn]

Okay, this interesting. The checks are pending now. Maybe it had to do with the WIP, although very odd that something that I have installed could mess with the checks on this organisation. Might try to verify by enabling WIP again later today and force pushing again. If that is indeed the case I'll contact GitHub support about it.

[jdbruijn]

Weird, I enabled WIP again and force pushed again to check, but now passed. So I don't know what was going on, I still suspect something with WIP.

Anyhow, the tests are now working, and have passed.

[escapedcat]

Thanks a lot for teh digging @jdbruijn ! Weird stuff. Will merge.