[#12194] Add simple workflow to vet pull requests

[zhaojj2209]

Fixes #12194
Part of #11383

Adds simple Github Actions workflow using actions/github-script to check PRs. The bot currently checks for the following:

• Title: starts with issue number in square brackets, followed by a space
• Description: contains either "Fixes" or "Part of", followed by the issue number. Only "Fixes" is checked since it is the keyword used in our PR template.

More checks can be added down the line as and when needed. The bot also only checks PRs that are newly opened/reopened, so as to avoid spam.

[github-actions]

Hi @zhaojj2209, thank you for your interest in contributing to TEAMMATES!
However, your PR does not appear to follow our contribution guidelines:

• Title must start with the issue number the PR is fixing in square brackets, e.g. [#<issue-number>]
• Description must reference the issue number the PR is fixing, e.g. Fixes #<issue-number> (or Part of #<issue-number> if the PR does not addres the issue fully)

Please address the above before we proceed to review your PR.

[samuelfangjw]

Seems like this doesn't check the title/pr after it is edited. Is this something we would want?

[zhaojj2209]

Seems like this doesn't check the title/pr after it is edited. Is this something we would want?

Github Actions has an edited type for PRs which I believe is triggered on editing PR title/body, but I intentionally left it out. Back when the old bot was active, there was a case where a contributor opened a PR then proceeded to spam title/description edits, resulting in maintainers watching the repo being spammed with comment notifications. There is therefore a trade-off between either higher workload for the maintainers (if the action does not rerun on edit) or higher risk of spam (if the action does rerun on edit).

@damithc @wkurniawan07 Would appreciate your input on this!

[samuelfangjw]

Github Actions has an edited type for PRs which I believe is triggered on editing PR title/body, but I intentionally left it out. Back when the old bot was active, there was a case where a contributor opened a PR then proceeded to spam title/description edits, resulting in maintainers watching the repo being spammed with comment notifications. There is therefore a trade-off between either higher workload for the maintainers (if the action does not rerun on edit) or higher risk of spam (if the action does rerun on edit).

Have similar thoughts, my opinion is it's ok to leave it as such. Maintainers can still manually verify/edit if there are issues.

[wkurniawan07]

@zhaojj2209 I have no strong opinion on rerun on edit. As you have identified, either one has its own set of pros/cons.

Only "Fixes" is checked since it is the keyword used in our PR template.

The old bot checks for all 9 acceptable keywords, so it's better to retain the behaviour here.