Repository navigation
feat(issues)!: retire completed stale triage rollout input - #813
Conversation
@coderabbitai review |
|
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 10 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The authenticated included-review refusal occurred at 2026-10-29T21:38:11Z and states a 10-minute reset. Scope: this repository and requesting author. The native guard confirms no actual review at this head. Advancing to Codex; the fresh lane-health read reports a later successful Codex review, so the earlier account refusal is no longer applicable. |
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Code coverage overviewLanguages: Go, C# Go / code-coverage/test
C# / code-coverage/dotnet
Go / code-coverage/go
View coverage of the 1 most impacted file.
ℹ️ Calculations represent line coverage. Results may change as calculations are updated. Updated |
|
Codex Review: Didn't find any major issues. 🚀 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Ready at Protected merge, actual publication and native source-pilot execution remain required. #808 stays open through final caller adoption. |
Published v19.0.0 at protected merge |
Why
The inactive-issue policy has completed its staged rollout, so the temporary rollout control can be retired.
What
Keep the agreed reminders, closure and recovery while simplifying adoption to the permanent policy.
Part of #808
💥 Breaking change: existing adopters must remove the temporary rollout setting when upgrading.