chore: deprecate unused workflow

[GabrielDrapor]

User description

https://github.com/pathintegral-institute/mcpm.sh/actions/runs/17486979191/workflow

---

PR Type

Other

---

Description

• Deprecate MCP Server Info Bot workflow

• Change trigger from issue labels to manual dispatch

• Disable workflow execution with conditional logic

• Update workflow name to indicate deprecation

---

Diagram Walkthrough

flowchart LR
  A["Issue Label Trigger"] -- "replaced by" --> B["Manual Dispatch Trigger"]
  B -- "with condition" --> C["Force Run Input"]
  C -- "disabled by" --> D["False Condition"]
  D --> E["Workflow Disabled"]

Loading

File Walkthrough

	Relevant files
Configuration changes	mcp-server-info-bot.yml Deprecate and disable MCP Server Info Bot workflow              .github/workflows/mcp-server-info-bot.yml Updated workflow name to indicate deprecation Changed trigger from issue labels to manual workflow dispatch Added force_run input parameter with default false Disabled workflow execution with conditional logic +8/-4

---

Summary by CodeRabbit

• Chores
  • Deprecated the MCP Server Info Bot workflow and updated its name to clearly indicate deprecation.
  • Replaced automatic issue-based triggering with a manual run option.
  • Added a force-run input to allow explicit manual execution when needed.
  • Ensured the workflow is effectively disabled by default to prevent unintended runs.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Renames and disables a deprecated GitHub Actions workflow. Replaces the issues-labeled trigger with a manual workflow_dispatch that includes a force_run input. Adds an if condition ensuring the job never runs by requiring force_run to be 'true' and appending && false.

Changes

Cohort / File(s)	Summary
Deprecated workflow disablement \.github/workflows/mcp-server-info-bot.yml	Rename to "MCP Server Info Bot (DEPRECATED)"; replace issues:labeled trigger with workflow_dispatch (input: force_run, default 'false'); update job if to github.event.inputs.force_run == 'true' && false to keep it disabled.

Sequence Diagram(s)

sequenceDiagram
    actor Maintainer
    participant GH as GitHub Actions
    participant Job as scrape-and-update job

    Maintainer->>GH: workflow_dispatch(force_run)
    GH->>Job: Evaluate if: (force_run == 'true' && false)
    alt Condition false
        GH--xJob: Skip job (workflow deprecated)
    else Condition true (unreachable)
        Job->>Job: Execute steps
    end

    note over GH,Job: The added "&& false" ensures the job never runs.

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

Review effort 2/5

Poem

I twitch my whiskers at the switch,
A bygone bot now sleeps in glitch—
Flip to dispatch? The gate says “no,”
With && false, it will not go.
I thump, I nod, deprecation’s done—
On to new fields, I hop and run! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 793e160 and a30b7f3.

📒 Files selected for processing (1)

• .github/workflows/mcp-server-info-bot.yml (1 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch Jiarui/workflow-fix

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Logic Always False The job condition uses "github.event.inputs.force_run == 'true' && false", which will prevent the job from ever running, even when force_run is 'true'. Confirm this is intentional; if you want a soft-disable with an escape hatch, remove "&& false". if: github.event.inputs.force_run == 'true' && false # Disable this deprecated workflow steps: Input Requirement The manual input "force_run" is marked required with default 'false'. In GitHub Actions, required + default can be redundant/confusing; consider making it optional or removing default to force an explicit choice. inputs: force_run: description: 'Force run this deprecated workflow (not recommended)' required: true default: 'false'

[qodo-merge-pro]

PR Code Suggestions ✨

No code suggestions found for the PR.

[mcpm-semantic-release]

🎉 This PR is included in version 2.8.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀