Add Repo Automator action

[jeffpaul]

What?

This PR adds a GitHub Action workflow file for the https://github.com/10up/action-repo-automator action. Now that we're seeing an influx of issues and PRs, the day-to-day effort from @dkotter and myself to maintain this repo needs some operational support. This workflow attempts to help in that regard.

Copilot summary

This pull request introduces a new GitHub Actions workflow called Repo Automator to automate pull request and issue management tasks. The workflow is triggered by various events on the develop branch and uses the 10up/action-repo-automator action to enforce PR review processes and provide automated feedback.

Workflow automation and PR management:

• Adds a .github/workflows/repo-automator.yml file that configures the Repo Automator workflow to automatically label, comment, and assign reviewers to pull requests and issues on the develop branch using the 10up/action-repo-automator action.
• Sets up permissions and triggers for the workflow to respond to issue creation, pushes, and several pull request events (opened, edited, synchronized, draft status changes) on the develop branch.
• Configures automated labels (Needs Feedback, Needs Code Review, Needs Refresh), custom comments for missing PR template information or merge conflicts, and assigns the ai-maintainers team as reviewers.

Why?

How?

Use of AI Tools

AI assistance: none, besides the generated Copilot summary in the PR description.

Testing Instructions

Screenshots or screencast

Before	After

Changelog Entry

Developer - Add Repo Automator workflow file.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: jeffpaul <jeffpaul@git.wordpress.org>
Co-authored-by: justlevine <justlevine@git.wordpress.org>
Co-authored-by: dkotter <dkotter@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

✅ WordPress Plugin Check Report

✅ Status: Passed

📊 Report

All checks passed! No errors or warnings found.

---

🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.50%. Comparing base (a3666fe) to head (239a84c).

Additional details and impacted files

@@            Coverage Diff             @@
##             develop     #765   +/-   ##
==========================================
  Coverage      75.50%   75.50%           
  Complexity      2086     2086           
==========================================
  Files             99       99           
  Lines           8626     8626           
==========================================
  Hits            6513     6513           
  Misses          2113     2113           

Flag	Coverage Δ
unit	75.50% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[jeffpaul]

@jeffpaul thanks for the PR! Could you please fill out the PR template with description, AI tool usage, and changelog information so that we can properly review and merge this?

Bah, seems we might need to adjust what the Repo Automator thinks the template should be here.

[justlevine]

Bah, seems we might need to adjust what the Repo Automator thinks the template should be here.

I was about to ask: if it can't be configured to enforce the whole template, could it least scan for the AI Disclosure section?

[dkotter]

Bah, seems we might need to adjust what the Repo Automator thinks the template should be here.

Yeah, I believe the template verification logic is hardcoded to match what we use on our OSS projects. Will likely need upstream changes to that in order to be of full use here

[jeffpaul]

Some superpowers work with Claude and now 10up/action-repo-automator#136 is open. Once some sort of update is ready in Repo Automator we can update to account for our PR template formatting here.

[jeffpaul]

Bah, looks like the Repo Automator update only shows failures within the job run itself, but doesn't add those as review comments. I'll have to look at updating that upstream and then adjusting here once that's ready. Sigh.

e.g. https://github.com/WordPress/ai/actions/runs/28964003832/job/85942384827?pr=765

Error: Please fill out the Why? section of the PR template
Error: Please fill out the Testing Instructions section of the PR template

[github-actions]

@jeffpaul thanks for the PR! Could you please fill out the PR template with description, AI tool usage, and changelog information so that we can properly review and merge this?

[dkotter]

@jeffpaul Looking at the run, seems it only adds a comment if there isn't an existing comment (which is probably worth discussing, seems like a new comment or at least updating the existing comment would be nice).

There was already a comment on this PR so I deleted it and re-ran the action and do see a new comment added. BUT the comment doesn't contain the error messages we want, seems to just be a generic error. That is likely an upstream fix