Skip to content
This repository was archived by the owner on Sep 29, 2026. It is now read-only.

docs: archived - #4165

Merged
mergify[bot] merged 1 commit into
mainfrom
docs-archived
Sep 29, 2026
Merged

mergify[bot] merged 1 commit into
mainfrom
docs-archived

Conversation

@ryanrozich

Copy link
Copy Markdown
Contributor

Marks the repository archived at the top of the README, pointing to catalyst-dev-skills and catalyst-cloud-skills, ahead of archiving the repository (Ryan's decision, via Lantern). No code changes.

🤖 Generated with Claude Code

Mark the repository archived at the top of the README, pointing to catalyst-dev-skills and catalyst-cloud-skills.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-29T10:16:51.120262Z 804ee80 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@mergify

mergify Bot commented Sep 29, 2026

Copy link
Copy Markdown

Merge Protections

🟢 All 2 merge protections satisfied — ready to merge.

Show 2 satisfied protections

🟢 no unresolved review threads before merge

  • #review-threads-unresolved=0

🟢 title follows the Conventional-Commit convention

  • title~=^(feat|fix|chore|docs|style|refactor|perf|test|build|ci|revert)(\((dev|meta|pm-ops|legacy|foundry)\))?!?:

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Hooray!

Reviewed commit: 804ee80444

ℹ️ About Codex in GitHub

Your team has set up Codex to 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 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@ryanrozich ryanrozich added the queue:ready Coordinator-verified: threads resolved, hand-steps done — Mergify may queue and merge label Sep 29, 2026
@mergify mergify Bot added the queued label Sep 29, 2026
@mergify

mergify Bot commented Sep 29, 2026 •

Copy link
Copy Markdown

Merge Queue Status

  • ✅ Entered queue — 2026-09-29 10:24 UTC · Rule: default · triggered by rule enqueue when a lane marks a PR ready
  • ✅ Checks skipped · PR is already up-to-date
  • ✅ Merged — 2026-09-29 10:24 UTC · at 155ba81b448f752036407d67181962f43b1c0b2e · squash

This pull request spent 13 seconds in the queue, including 2 seconds running CI.

Required conditions to merge
  • #review-threads-unresolved = 0 [🛡 GitHub repository ruleset rule main branch protection]
  • #review-threads-unresolved=0
  • -check-failure=quality
  • -check-pending=quality
  • -draft
  • -files~=^\.github/workflows/publish-
  • -files~=^\.mergify\.yml$
  • -files~=^plugins/dev/scripts/db-migrations/
  • -head~=^release-please--
  • base=main
  • github-review-approved [🛡 GitHub repository ruleset rule main branch protection]
  • label!=hold:hand-steps
  • label=queue:ready
  • all of [🛡 Merge Protections rule no unresolved review threads before merge]:
  • all of [🛡 Merge Protections rule title follows the Conventional-Commit convention]:
    • title~=^(feat|fix|chore|docs|style|refactor|perf|test|build|ci|revert)(\((dev|meta|pm-ops|legacy|foundry)\))?!?:
  • any of:
    • check-success=docs-gate
    • check-neutral=docs-gate
    • check-skipped=docs-gate
  • any of:
    • check-success=gitleaks
    • check-neutral=gitleaks
    • check-skipped=gitleaks
  • any of:
    • check-success=agents-md-gate
    • check-neutral=agents-md-gate
    • check-skipped=agents-md-gate
  • any of:
    • check-success=audit-references
    • check-neutral=audit-references
    • check-skipped=audit-references
  • any of:
    • check-success=check-versions
    • check-neutral=check-versions
    • check-skipped=check-versions
  • any of:
    • check-skipped=execution-core-unit-tests
    • check-neutral=execution-core-unit-tests
    • check-success=execution-core-unit-tests
  • any of:
    • check-success=packaging-gate
    • check-neutral=packaging-gate
    • check-skipped=packaging-gate
  • any of:
    • check-success=skills-gate
    • check-neutral=skills-gate
    • check-skipped=skills-gate
  • any of:
    • check-success=check-plugin-manifest-parity
    • check-neutral=check-plugin-manifest-parity
    • check-skipped=check-plugin-manifest-parity
  • any of [🛡 GitHub repository ruleset rule main branch protection]:
    • check-success = docs-gate
    • check-neutral = docs-gate
    • check-skipped = docs-gate
  • any of [🛡 GitHub repository ruleset rule main branch protection]:
    • check-success = gitleaks
    • check-neutral = gitleaks
    • check-skipped = gitleaks
  • any of [🛡 GitHub repository ruleset rule main branch protection]:
    • check-success = agents-md-gate
    • check-neutral = agents-md-gate
    • check-skipped = agents-md-gate
  • any of [🛡 GitHub repository ruleset rule main branch protection]:
    • check-success = audit-references
    • check-neutral = audit-references
    • check-skipped = audit-references
  • any of [🛡 GitHub repository ruleset rule main branch protection]:
    • check-success = check-versions
    • check-neutral = check-versions
    • check-skipped = check-versions
  • any of [🛡 GitHub repository ruleset rule main branch protection]:
    • check-skipped = execution-core-unit-tests
    • check-neutral = execution-core-unit-tests
    • check-success = execution-core-unit-tests

@mergify
mergify Bot merged commit 155ba81 into main Sep 29, 2026
20 checks passed
@mergify mergify Bot removed the queued label Sep 29, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

queue:ready Coordinator-verified: threads resolved, hand-steps done — Mergify may queue and merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant