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>

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

[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?

[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 76.41%. Comparing base (ba6d4b8) to head (33ba085).

Additional details and impacted files

@@            Coverage Diff             @@
##             develop     #765   +/-   ##
==========================================
  Coverage      76.41%   76.41%           
  Complexity      1828     1828           
==========================================
  Files             87       87           
  Lines           7764     7764           
==========================================
  Hits            5933     5933           
  Misses          1831     1831           

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

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?