fix(ci): remove ignore-pr-updates that marks active PRs as stale

[CatherineSue]

Description

Problem

ignore-pr-updates: true in actions/stale uses creation date only, ignoring all activity. This caused active PRs (e.g., #586 with commits yesterday) to be marked stale simply because they were created >14 days ago.

Solution

Remove the flag to use default updated_at-based tracking.

Test Plan

Trigger manually and verify active PRs are not marked stale.

Summary by CodeRabbit

• Chores
  • Updated stale pull request tracking configuration to consider recent activity and updates when determining staleness status. This ensures pull requests with ongoing changes are not marked as stale based solely on label history.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: c784758b-c68b-4528-9689-54b13bab2d5b

📥 Commits

Reviewing files that changed from the base of the PR and between ebdf26b and dac3530.

📒 Files selected for processing (1)

• .github/workflows/stale.yml

---

📝 Walkthrough

Walkthrough

Removed the ignore-pr-updates: true setting and its explanatory comment from the stale PRs GitHub Actions workflow. This allows PR staleness calculations to account for PR activity and updated_at timestamps rather than exclusively relying on stale label creation/update tracking.

Changes

Cohort / File(s)	Summary
Stale Workflow Configuration .github/workflows/stale.yml	Removed ignore-pr-updates: true setting and associated comment, allowing PR activity to influence staleness decisions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• fix(ci): fix mergify stale/close rules that never trigger #798 — Also modifies the stale workflow configuration to address how PR activity and updated_at affect staleness handling.

Suggested labels

ci

Suggested reviewers

• key4ng
• slin1237
• XinyueZhang369

Poem

🐰 A bunny bounces with delight,
Staleness rules fade from sight!
Updates now dance, no longer ignored,
Fresh PRs flourish—activity restored! ✨

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/stale-workflow-ignore-updates

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: dac3530a25

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Don't let bot conflict updates reset the stale timer

Removing ignore-pr-updates puts actions/stale back on GitHub's updated_at clock for both days-before-pr-stale and days-before-pr-close (per the action README), so non-human PR updates now count as activity again. In this repo, .github/mergify.yml:57-86 automatically adds/removes needs-rebase and posts a comment when a PR's conflict status changes, which can happen solely because main moved. Those bot label/comment updates will now restart the 14/16-day timers, so abandoned PRs with conflict churn can stay open indefinitely even when the author has been inactive.

Useful? React with 👍 / 👎.