Add a worfklow to check if contributor exists in contributors.yaml

[cmainas]

Add a workflow to check if the author of the PR exists in https://github.com/urunc-dev/urunc/blob/main/.github/contributors.yaml

[Anshumancanrock]

hii @cmainas , I would like to work on this one. Could you please assign this to me? Thanks.

[cmainas]

Hello @Anshumancanrock ,

feel free to work on this, but please share your approach here first and test before opening a PR.

[sahanaxzy]

Hello @cmainas, I would like to work on this too...

My approach:

• Create a new workflow file .github/workflows/check-contributor.yml
• Trigger on pull_request_target event
• Use actions/checkout to fetch the repo
• Parse .github/contributors.yaml to extract the list of GitHub usernames
• Compare github.event.pull_request.user.login against the list
• If the author is not found, fail the check with a descriptive message

I'll test it locally before opening a PR.

[Anshumancanrock]

Hi @cmainas, Here's my approach:

Add a check-contributor job to the existing validate-files-and-commits.yml instead of creating a separate workflow.

How it works:

• Extract github.event.pull_request.user.login and normalize it using the same sed logic that nubificus/git-trailers uses (strip [bot] suffix, app/ prefix)
• Primary lookup: match the normalized username as a YAML key in .github/contributors.yaml
• Bot fallback: if no key match, search by name field
• Fail with a clear message telling the contributor exactly what to add

Key details:

• Runs only on PR events (if: github.event.pull_request != null), skipped for manual/scheduled triggers
• Checks out inputs.ref (the PR branch), so new contributors can add themselves to contributors.yaml in the same PR
• Uses env: block for the author variable, not inline ${{ }}, to avoid script injection

I've tested the logic locally against the current contributors.yaml and it handles all the edge cases correctly.
Happy to open a PR whenever you're good with the approach.

[cmainas]

Hello all, the workflow should not run in pull_request_target there is no reason for that. I agree with @Anshumancanrock to add it as a job in validate-files-and-commits.yml. For the logic use as a reference https://github.com/nubificus/git-trailers/blob/main/action.yml. So @Anshumancanrock please test it free and if it works feel free to open a PR. Make sure to add the respective links to the actions that were executed.

[Anshumancanrock]

Thanks @cmainas , The implementation is ready and already tested locally. Opening the PR now.