MDBF-1234: pull request submission trigger to verify the format

[gkodinov]

Implement a pull request submission trigger running when files in lists/ are changed to verify if their format is parseable.

Note that this PR is based on #1

[Copilot]

Pull request overview

This PR introduces a GitHub Actions workflow that runs on pull requests affecting lists/** to validate that list files follow a parseable, consistent Markdown bullet/link format, and adds initial list files (reviewers, maintainers, committers).

Changes:

• Added a pull_request workflow to detect changed files under lists/ and validate bullet/link formatting.
• Added lists/reviewers.md, lists/maintainers.md, and lists/committers.md with GitHub profile links.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.

File	Description
.github/workflows/check-lists-format.yml	Adds the PR-triggered validation workflow for lists/** changes.
lists/reviewers.md	Adds the reviewers list in Markdown bullet/link format.
lists/maintainers.md	Adds the maintainers list in Markdown bullet/link format.
lists/committers.md	Adds the committers list in Markdown bullet/link format.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[vuvova]

Looks very complex. I thought it'd be a one-liner like

grep '^ *\* \+' lists/*|grep -v ': *\* \+\[[^]]\+\](https://github.com/.*)'

[vuvova]

could it be simplified?

[gkodinov]

could it be simplified?

It probably can be simplified. But what is the point?
I am confident it works as expected. And I like the extra verbosity.
Besides it's doing more or less the same, but in a loop and for each file separately:

            bullet_count=$(grep -cE "$BULLET_RE" "$file" || true)
            link_count=$(grep -cE "$LINK_RE"  "$file" || true)

            echo "File: $file"
            echo "  lines matching ^[[:space:]]*\*          : $bullet_count"
            echo "  lines matching the GitHub-link pattern  : $link_count"

            if [ "$bullet_count" -ne "$link_count" ]; then
              echo "::error file=$file::Bullet-line count ($bullet_count) does not equal properly-formatted GitHub-link count ($link_count)"
              FAIL=1
            else
              echo "  ? counts match"
            fi

[vuvova]

I know it's doing more or less the same. But it's 40 lines instead of one and the reading speed is generally proportional to the number of lines. It's 40x more lines to read and understand. Only to arrive at conclusion that it's just a hand-coded grep|grep -v.

[gkodinov]

I know it's doing more or less the same. But it's 40 lines instead of one and the reading speed is generally proportional to the number of lines. It's 40x more lines to read and understand. Only to arrive at conclusion that it's just a hand-coded grep|grep -v.

Alright. This is a stylistic thing, but there's no point in arguing if I want the job done. grep | grep -v it is.