Skip to content

chore: remove obsolete workflows and align stale messaging#402

Merged
jwm4 merged 1 commit intomainfrom
chore/remove-obsolete-workflows
May 8, 2026
Merged

chore: remove obsolete workflows and align stale messaging#402
jwm4 merged 1 commit intomainfrom
chore/remove-obsolete-workflows

Conversation

@kami619
Copy link
Copy Markdown
Collaborator

@kami619 kami619 commented May 8, 2026

Summary

  • Remove obsolete workflows: agentready-dev-issue-pr.yml, agentready-dev.yml, pr-review.yml, and docs.yml.
  • Update stale issue/PR messages in stale-issues.yml to match configured thresholds: 60 days stale, 30 days to close (90 days total).

Related issues

Test plan

  • Verify removed workflow files are no longer present under .github/workflows/.
  • Verify stale workflow text now references 60/30/90-day thresholds.
  • Run diagnostics for the edited workflow file.

Made with Cursor

Drop outdated development, docs, and PR review workflows that are no longer used by this repository.
Update stale issue/PR messages to match the configured 60-day stale and 30-day close thresholds.

Co-authored-by: Cursor <cursoragent@cursor.com>
@kami619 kami619 requested a review from jwm4 May 8, 2026 02:33
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 8, 2026

Warning

.coderabbit.yaml has a parsing error

The CodeRabbit configuration file in this repository has a parsing error and default settings were used instead. Please fix the error(s) in the configuration file. You can initialize chat with CodeRabbit to get help with the configuration file.

💥 Parsing errors (1)
Validation error: String must contain at most 250 character(s) at "tone_instructions"
⚙️ Configuration instructions
  • Please see the configuration documentation for more information.
  • You can also validate your configuration using the online YAML validator.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Walkthrough

This PR removes four GitHub Actions workflows (agentready-dev-issue-pr.yml, agentready-dev.yml, pr-review.yml, and docs.yml) and updates stale issue/PR timeline thresholds. The removed workflows include AI-assisted issue-to-PR automation, PR review actions, and documentation link checking. The stale-issues workflow now waits 60 days before marking issues/PRs stale and 30 days more before closure.

Changes

GitHub Actions Workflow Updates

Layer / File(s) Summary
Workflow Removals
.github/workflows/agentready-dev-issue-pr.yml, .github/workflows/agentready-dev.yml, .github/workflows/pr-review.yml, .github/workflows/docs.yml
Four workflows removed: agentready-dev-issue-pr.yml (796 lines) for automating issues to draft PRs, agentready-dev.yml (355 lines) for handling @agentready-dev mentions, pr-review.yml (83 lines) for Claude-based PR reviews, and docs.yml (40 lines) for lychee-based link checking on documentation PRs.
Stale Issue Configuration Update
.github/workflows/stale-issues.yml
days-before-stale increased from 21 to 60 days; days-before-close increased from 7 to 30 days, extending total inactivity window to 90 days. Stale and closure messages updated to reflect new 60-day and 90-day thresholds for both issues and PRs.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main changes: removing obsolete workflows and updating stale messaging thresholds.
Description check ✅ Passed The description clearly explains what was removed and what was updated, relates directly to the changeset, and provides context.
Linked Issues check ✅ Passed The PR addresses issue #397 by removing docs.yml workflow and updates stale-issues.yml messaging to reflect configured thresholds as intended.
Out of Scope Changes check ✅ Passed All changes are in scope: four workflow removals align with the cleanup objective, and stale-issues.yml updates align with messaging alignment objective.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/remove-obsolete-workflows

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

  • Generate code and open pull requests
  • Plan features and break down work
  • Investigate incidents and troubleshoot customer tickets together
  • Automate recurring tasks and respond to alerts with triggers
  • Summarize progress and report instantly

Built for teams:

  • Shared memory across your entire org—no repeating context
  • Per-thread sandboxes to safely plan and execute work
  • Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started


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.

❤️ Share

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

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/stale-issues.yml:
- Line 21: The inline comment next to the days-before-stale setting is
incorrect; update the comment to match the configured value by changing the
comment for days-before-stale from “30 days before 90-day close” to “60 days
before 90-day close” (referencing the days-before-stale key in the workflow).
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: c70e4801-08f0-4f55-ae5f-be39b3e76b03

📥 Commits

Reviewing files that changed from the base of the PR and between 4f99a69 and 84d7675.

📒 Files selected for processing (5)
  • .github/workflows/agentready-dev-issue-pr.yml
  • .github/workflows/agentready-dev.yml
  • .github/workflows/docs.yml
  • .github/workflows/pr-review.yml
  • .github/workflows/stale-issues.yml
💤 Files with no reviewable changes (4)
  • .github/workflows/docs.yml
  • .github/workflows/pr-review.yml
  • .github/workflows/agentready-dev.yml
  • .github/workflows/agentready-dev-issue-pr.yml

Comment thread .github/workflows/stale-issues.yml
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 8, 2026

📈 Test Coverage Report

Branch Coverage
This PR 75.4%
Main 75.4%
Diff ✅ +0%

Coverage calculated from unit tests only

Copy link
Copy Markdown
Contributor

@jwm4 jwm4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All changes look good to me. The one complaint from CodeRabbit seems to be wrong (60 is 30 days from 90). I will merge this now.

@jwm4 jwm4 merged commit 3faebec into main May 8, 2026
13 checks passed
@jwm4 jwm4 deleted the chore/remove-obsolete-workflows branch May 8, 2026 12:29
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 8, 2026

🎉 This PR is included in version 2.35.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove or rethink the link checker workflow

2 participants