The one and only agent harness for complex codebases. Project memory, planning, execution, and verified completion inside Codex.
JavaScript aiai-agentsclaudeclaude-codeclicodexdeveloper-toolslazylazycodexoh-my-openagentomoopenaiorchestrationtypescript
ci: reword PR guidance and add agent redirect prompt
YeonGyu-Kima596185f44e4
diff --git a/.github/workflows/pr-source-guidance.yml b/.github/workflows/pr-source-guidance.ymlindex c99df480..488884b3 100644--- a/.github/workflows/pr-source-guidance.yml+++ b/.github/workflows/pr-source-guidance.yml@@ -17,12 +17,19 @@ jobs:env:GH_TOKEN: ${{ github.token }}PR_NUMBER: ${{ github.event.pull_request.number }}+ PR_TITLE: ${{ github.event.pull_request.title }}run: |set -euo pipefail+ PR_URL="https://github.com/$GITHUB_REPOSITORY/pull/$PR_NUMBER"+body="$(mktemp)"- cat > "$body" <<'MARKDOWN'- Thanks for the PR! This repository is a generated distribution mirror, so PRs here cannot be merged. Please open your PR against [oh-my-openagent](https://github.com/code-yeongyu/oh-my-openagent) instead.+ cat > "$body" <<MARKDOWN+ Thanks for the PR! Changes to LazyCodex land through [oh-my-openagent](https://github.com/code-yeongyu/oh-my-openagent) — could you open this against [omo-codex](https://github.com/code-yeongyu/oh-my-openagent/tree/dev/packages/omo-codex) over there instead? PRs in this repository can't be merged.++ If you're working with a coding agent, prompt it like this:++ > I opened $PR_URL ("$PR_TITLE") against code-yeongyu/lazycodex, but changes there land through code-yeongyu/oh-my-openagent, where the Codex implementation lives under packages/omo-codex. Read my original PR, then open an equivalent PR against code-yeongyu/oh-my-openagent. In the new PR body, link the original PR ($PR_URL), explain that it was first opened against lazycodex, and describe in detail what that PR changed and why.MARKDOWNgh pr close "$PR_NUMBER" --repo "$GITHUB_REPOSITORY" --comment "$(cat "$body")"