micro--go-micro
Asim Aslam
b45c94e201
Codex's make_pr tool in the Cloud sandbox is a no-op stub — it records the PR title/body and returns them "for downstream consumption" (the manual "Create PR" click), but never pushes a branch or calls the GitHub API. That is why "make_pr called, nothing happened": the tool literally cannot open a PR. With the gh CLI now installed in the Codex setup and origin pointed at the repo, the dispatch tells Codex to push and open the PR itself (git push + gh pr create) instead of relying on make_pr. Claude-Session: https://claude.ai/code/session_01CmdEY7pYmV5zzwCjNJ4ykL Co-authored-by: Claude <noreply@anthropic.com>
63 行
3.7 KiB
YAML
63 行
3.7 KiB
YAML
name: Continuous Improvement
|
|
|
|
# Durable backbone for the autonomous improvement loop
|
|
# (see internal/docs/CONTINUOUS_IMPROVEMENT.md).
|
|
#
|
|
# A Claude Max subscription provides no API key for CI, so the loop is driven by
|
|
# Codex rather than Claude Code: on a cadence this opens a fresh tracking issue and
|
|
# posts an @codex instruction on it, and Codex runs one improvement increment + opens
|
|
# a PR. (See the per-issue rationale below.)
|
|
#
|
|
# Codex does NOT respond to comments authored by the github-actions bot, so the
|
|
# dispatch is GATED on a CODEX_TRIGGER_TOKEN secret (a PAT for a user account Codex
|
|
# follows). Until that secret is set the workflow runs but no-ops — this avoids
|
|
# piling up @codex comments that Codex silently ignores. The moment the secret is
|
|
# added the loop activates with no further change.
|
|
#
|
|
# Each run opens a FRESH issue and dispatches Codex there, rather than re-commenting
|
|
# on one tracker issue. Codex derives its PR branch name from the triggering issue's
|
|
# context, so repeated dispatches on a single issue all collapse onto one branch name
|
|
# (codex/github-mention-<that-issue-slug>) — the first increment opens a PR, the rest
|
|
# collide on the occupied branch and silently fail to open one. A unique issue per
|
|
# run gives each increment its own branch and a clean PR. The dispatch asks Codex to
|
|
# "Closes #<issue>" so each tracking issue auto-closes when its PR merges.
|
|
|
|
on:
|
|
workflow_dispatch: {}
|
|
schedule:
|
|
- cron: "29 * * * *" # hourly, off-minute (tune as needed)
|
|
|
|
permissions:
|
|
issues: write
|
|
|
|
concurrency:
|
|
group: continuous-improvement
|
|
cancel-in-progress: false
|
|
|
|
jobs:
|
|
dispatch:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Open a fresh increment issue and dispatch Codex
|
|
env:
|
|
GH_TOKEN: ${{ secrets.CODEX_TRIGGER_TOKEN || github.token }}
|
|
HAS_TRIGGER_TOKEN: ${{ secrets.CODEX_TRIGGER_TOKEN != '' }}
|
|
REPO: ${{ github.repository }}
|
|
RUN_NUMBER: ${{ github.run_number }}
|
|
run: |
|
|
if [ "$HAS_TRIGGER_TOKEN" != "true" ]; then
|
|
echo "CODEX_TRIGGER_TOKEN is not set — skipping dispatch."
|
|
echo "Codex ignores comments from the github-actions bot, so posting now"
|
|
echo "would only create noise. Add a CODEX_TRIGGER_TOKEN secret (a PAT for"
|
|
echo "a user account Codex follows) to activate the loop."
|
|
exit 0
|
|
fi
|
|
# A unique issue per run → Codex derives a unique branch → no collisions.
|
|
ISSUE_URL=$(gh issue create --repo "$REPO" \
|
|
--title "Continuous improvement increment #$RUN_NUMBER" \
|
|
--body "Autonomous continuous-improvement increment. North Star: internal/docs/THESIS.md; charter: internal/docs/CONTINUOUS_IMPROVEMENT.md. Tracker: #3024.")
|
|
ISSUE_NUM="${ISSUE_URL##*/}"
|
|
echo "Opened issue #$ISSUE_NUM — dispatching Codex."
|
|
gh issue comment "$ISSUE_NUM" --repo "$REPO" --body \
|
|
"@codex Run one continuous-improvement increment per internal/docs/CONTINUOUS_IMPROVEMENT.md, aligned to the North Star in internal/docs/THESIS.md (the holistic services → agents → workflows lifecycle). Pick the single highest-value roadmap/issue/improvement-radar item that advances that thesis, implement it, and verify \`go build ./...\`, \`go test ./...\`, and \`golangci-lint run ./...\`. Then open the PR YOURSELF from the shell — do NOT use the make_pr tool (in this environment it only records metadata and never creates a PR). Run \`git push -u origin HEAD\` then \`gh pr create --base master --title \"<title>\" --body \"<body, including 'Closes #$ISSUE_NUM'>\"\`; the gh CLI is installed and authenticated and origin points to $REPO. One concern per PR; stay out of brand/positioning copy and breaking public API."
|