Add more nuanced unmet requirements for external PRs

[tidy-dev]

Summary

Adds opt-in extended PR screening to the triage-pr-requirements.yml reusable workflow. When enable_pr_screening: true is set, four new behaviors activate for external PRs:

Behavior	What happens	Default thresholds
Zero-change close	PRs with 0 file changes are instantly closed	—
Resubmission detection	Same-author PRs matching recently closed unmet-requirements PRs (file overlap, 30-day window) are closed	≥2 overlapping files
Small-fix fast-track	Small, well-described PRs skip unmet-requirements and go straight to review	≤30 LOC, ≤3 files, ≥100 char body
Large PR accelerated close	Large unsolicited PRs with no team reviews get a shorter close deadline	>200 LOC, >5 files, 3 days

All existing behavior is unchanged when enable_pr_screening is not set (default: false).

New Inputs

Input	Type	Default	Description
enable_pr_screening	boolean	false	Master toggle for all screening behaviors
fast_track_max_loc	number	30	Max lines changed for fast-track
fast_track_max_files	number	3	Max files changed for fast-track
fast_track_min_body	number	100	Min body length (normalized) for fast-track
fast_track_label	string	ready-for-review	Label applied to fast-tracked PRs
large_pr_min_loc	number	200	Min lines to trigger large PR path
large_pr_min_files	number	5	Min files to trigger large PR path
large_pr_days_until_close	number	3	Days before closing large PRs

Pipeline Order

spam (zero-change) → resubmission → requirements check → fast-track → large PR → standard unmet-requirements

First match wins — subsequent steps are skipped.

Comment Improvements

• All unmet-requirements comments now show the specific reason upfront with full requirements in a collapsed <details> block
• Large PR comments include LOC/file stats and direct guidance to open an issue first
• Fast-tracked PRs get an encouraging message with a note about linking issues

Scheduled Close Enhancements

The close-unmet-requirements scheduled job now checks PR size at close time:

• Standard PRs: closed after days_until_close (default 7 days)
• Large PRs (when screening enabled): closed after large_pr_days_until_close (default 3 days)

This ensures the accelerated timeline promised in the comment is actually enforced.

Security & Robustness

• Review bypass protection: Large PR detection filters reviews by authorAssociation (MEMBER/OWNER/COLLABORATOR only) — external drive-by reviews can't defeat the accelerated close
• Self-hosted runner safety: Resubmission detection uses $RUNNER_TEMP instead of /tmp to avoid cross-job interference
• Missing label guard: Fast-track label application uses || true so a missing label doesn't abort the job
• Configurable fast-track label: New fast_track_label input (default: ready-for-review) so consumers can customize

Testing

Tested all 4 paths in tidy-dev/playground with a workflow referencing this branch:

Test PR	Scenario	Result
#12	Zero-change (empty commit)	✅ Instantly closed
#13	Large unsolicited (248 LOC, 8 files)	✅ unmet-requirements + 3-day message
#14	Small fix (1 LOC, 1 file, good body)	✅ ready-for-review label applied
#15	Standard unmet (medium, no help-wanted)	✅ unmet-requirements + 7-day message

Files Changed

• .github/workflows/triage-pr-requirements.yml — All new logic + scheduler enhancement
• example-usage/triage-prs.yml — Commented example showing opt-in usage
• README.md — Updated workflow description, labels table, and configurable inputs

[Copilot]

Pull request overview

Adds an opt-in “extended PR screening” mode to the reusable triage-pr-requirements.yml workflow to better handle external PRs (auto-close empty PRs, detect resubmissions, fast-track small fixes, and accelerate closure of large unsolicited PRs), while keeping existing behavior unchanged unless enabled.

Changes:

• Introduces new workflow_call inputs and screening steps (zero-change close, resubmission detection, small-fix fast-track, large PR path) in triage-pr-requirements.yml.
• Updates unmet-requirements/large-PR comment formatting to include a reason-first message with full requirements in a <details> block.
• Documents the opt-in feature in README and adds a commented example configuration.

Show a summary per file

File	Description
.github/workflows/triage-pr-requirements.yml	Adds opt-in screening logic, new inputs, updated commenting, and scheduled close adjustments.
example-usage/triage-prs.yml	Adds commented example showing how to enable screening via with: inputs.
README.md	Documents the new screening capability and updates labels/inputs tables accordingly.

Copilot's findings

Tip

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

Comments suppressed due to low confidence (1)

.github/workflows/triage-pr-requirements.yml:393

• This comment body is indented inside the quoted string, which will render as a Markdown code block and likely break the intended formatting (including the new <details> block). Use a heredoc/--body-file (without leading indentation) so the reasons and <details> collapse render properly.

          gh pr comment "$NUMBER" --body "Thanks for your pull request! Unfortunately, it doesn't meet the requirements for review:

          $REASONS

          **Please update your PR to address the above.** This PR will be automatically closed in **$DAYS days** if these requirements are not met.

          <details>
          <summary>Full contribution requirements</summary>

          1. Include a detailed description of what this PR does
          2. Link to an issue with the \`${{ inputs.help_wanted_label || 'help wanted' }}\` label (use \`Fixes #123\` or \`Closes #123\`)
          </details>"

• Files reviewed: 3/3 changed files
• Comments generated: 2