Skip to content

chore(branches): close obsolete t3code branches#11

Merged
isuttell merged 2 commits into
mainfrom
agents/cleanup-stale-branches
May 22, 2026
Merged

chore(branches): close obsolete t3code branches#11
isuttell merged 2 commits into
mainfrom
agents/cleanup-stale-branches

Conversation

@isuttell

@isuttell isuttell commented May 22, 2026

Copy link
Copy Markdown
Contributor

Summary

Risk

Docs-only. pnpm verify green (49/49 turbo tasks, all cached).

Test plan

  • pnpm verify
  • gh api repos/:owner/:repo/branches confirms no t3code/* branches remain

Co-Authored-By: Claude Opus 4.7 noreply@anthropic.com

Summary by CodeRabbit

  • Documentation
    • Updated project status to show no remaining open development branches and documented closure of obsolete branches.
    • Added a "Recently Completed" section summarizing branch clean-up and the marketing worker scaffold merge.
    • Renumbered the "Next Steps Backlog" for clarity (bootstrap hosting checklist moved to item 7).

Review Change Stack

Backlog item #7 in docs/ops/project-status.md asked to review and merge
t3code/7bcd4587 and t3code/5b6355f9. Both branches no longer exist on
origin (verified via git fetch and gh api repos/:owner/:repo/branches);
the underlying commits are unreachable. The only Apex/front-end work
that ever landed from the t3code family was PR #1 (the marketing
worker scaffold). Remove the stale references from project-status.md
and move the item to Recently Completed.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@isuttell isuttell temporarily deployed to pr-preview-11 May 22, 2026 03:37 — with GitHub Actions Inactive
@coderabbitai

coderabbitai Bot commented May 22, 2026

Copy link
Copy Markdown

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: e4fd8974-d6c7-4df6-89e1-7b3c0d55d265

📥 Commits

Reviewing files that changed from the base of the PR and between 09fe206 and 0e839d0.

📒 Files selected for processing (1)
  • docs/ops/project-status.md

Walkthrough

This PR updates the project status documentation to reflect the completion of t3code/* branch cleanup. The snapshot section now states no open t3code/* branches remain on main/origin. The backlog numbering shifts “Complete bootstrap hosting checklist” to item 7, and a new “Recently Completed” subsection documents the branch closures and verification steps used.

Poem

🐰 I hopped through commits, tidy and spry,

pruned old branches with a careful eye,
the status page now breathes relief,
lines renumbered, tidy and brief,
— a rabbit’s nibble, soft and sly.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'chore(branches): close obsolete t3code branches' accurately summarizes the main change—removing stale t3code branch references and documenting their closure in the project status document.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ 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 agents/cleanup-stale-branches

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
docs/ops/project-status.md (1)

184-184: ⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Update the item range to match the renumbered backlog.

After removing the t3code branches backlog item and renumbering, there are now only 7 items in the backlog (items 1-7). This line should be updated to reflect the correct range.

📝 Proposed fix
-Ordered. Each item has a verifiable Done. Items 1-5 close Phase 1; items 6-8 prep hosted ops and Phase 2.
+Ordered. Each item has a verifiable Done. Items 1-5 close Phase 1; items 6-7 prep hosted ops and Phase 2.
🤖 Prompt for 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.

In `@docs/ops/project-status.md` at line 184, Update the backlog item range text
in the sentence that currently reads "Items 1-5 close Phase 1; items 6-8 prep
hosted ops and Phase 2" to reflect the renumbered backlog of seven items—change
"items 6-8" to "items 6-7" so the sentence becomes "Items 1-5 close Phase 1;
items 6-7 prep hosted ops and Phase 2."
🤖 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 `@docs/ops/project-status.md`:
- Around line 232-237: Update the text under the "Close obsolete `t3code/*`
branches" section to disambiguate "this doc backlog item `#7`": replace or append
the phrase "this doc backlog item `#7`" with a clarifying qualifier such as "this
doc backlog item `#7` (former)" or "this doc backlog item `#7` — now removed" so
readers won't confuse it with the current backlog item `#7`; ensure the change
appears in the same paragraph that mentions the drives/backlog reference and
keep surrounding references (e.g., `t3code/7bcd4587`, `t3code/5b6355f9`, and PR
`#1`) intact.

---

Outside diff comments:
In `@docs/ops/project-status.md`:
- Line 184: Update the backlog item range text in the sentence that currently
reads "Items 1-5 close Phase 1; items 6-8 prep hosted ops and Phase 2" to
reflect the renumbered backlog of seven items—change "items 6-8" to "items 6-7"
so the sentence becomes "Items 1-5 close Phase 1; items 6-7 prep hosted ops and
Phase 2."
🪄 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: Pro Plus

Run ID: 7af6b806-7403-4336-b8b2-92d23919284c

📥 Commits

Reviewing files that changed from the base of the PR and between 82579a7 and 09fe206.

📒 Files selected for processing (1)
  • docs/ops/project-status.md

Comment thread docs/ops/project-status.md
@isuttell isuttell temporarily deployed to pr-preview-11 May 22, 2026 04:13 — with GitHub Actions Inactive
@isuttell isuttell merged commit bf7fe11 into main May 22, 2026
3 of 4 checks passed
isuttell added a commit that referenced this pull request May 22, 2026
PR #2 added `permissions: administration: write` to the cleanup
workflow, but `administration` is not a valid GITHUB_TOKEN scope. GitHub
rejected the workflow at evaluation time, silently dropping every
`pull_request.closed` event for PRs #2--#9 and accumulating eight
stale `preview/pr-N` Neon branches that tripped the 10-branch free-tier
cap (blocks PR #10/#11/#12 deploys with HTTP 422).

Drop the invalid permission and the `deleteAnEnvironment` step that
required it; rename the file so GitHub registers a fresh workflow id
instead of reusing the wedged record; validate the resolved PR number
is a positive integer before deleting anything.

Stale Neon branches still need a one-time operator purge -- agent is
forbidden from calling `neondatabase/delete-branch-action` autonomously.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
isuttell added a commit that referenced this pull request May 22, 2026
PR #2 added `permissions: administration: write` to the cleanup
workflow, but `administration` is not a valid GITHUB_TOKEN scope. GitHub
rejected the workflow at evaluation time, silently dropping every
`pull_request.closed` event for PRs #2--#9 and accumulating eight
stale `preview/pr-N` Neon branches that tripped the 10-branch free-tier
cap (blocks PR #10/#11/#12 deploys with HTTP 422).

Drop the invalid permission and the `deleteAnEnvironment` step that
required it; rename the file so GitHub registers a fresh workflow id
instead of reusing the wedged record; validate the resolved PR number
is a positive integer before deleting anything.

Stale Neon branches still need a one-time operator purge -- agent is
forbidden from calling `neondatabase/delete-branch-action` autonomously.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant