Skip to content

docs(repo): define branch lifecycle - #588

Merged
izadoesdev merged 1 commit into
stagingfrom
codex/branch-lifecycle
Aug 2, 2026
Merged

docs(repo): define branch lifecycle#588
izadoesdev merged 1 commit into
stagingfrom
codex/branch-lifecycle

Conversation

@izadoesdev

@izadoesdev izadoesdev commented Aug 2, 2026

Copy link
Copy Markdown
Member

Summary

  • define a short-lived, one-slice branch lifecycle for contributors and agents
  • make scope, ownership, dependencies, and overlap checks explicit in every PR
  • document rebase-first integration and safe worktree retirement

Repository settings applied

  • automatically delete merged source branches
  • protect staging: PR-only, resolved conversations, no force-pushes or deletion

Slice

  • Issue: maintainer workflow cleanup
  • Scope / owning surface: repository branch and PR lifecycle
  • Dependencies or overlapping PRs: None

Verification

  • bun run lint

  • bun run test (pre-push)

  • This branch started from current staging and does not include another unmerged PR.

  • This is one independently reviewable slice; unrelated cleanup or refactors are separate.

  • I checked open PRs for overlapping files, contracts, schemas, or deployment configuration.

  • This PR targets staging; after it closes, this branch will not be reused.


Summary by cubic

Defines a short-lived branch and PR lifecycle to keep work in small, linear slices. Makes scope, dependencies, and overlap checks explicit in every PR, and documents rebase-first integration and safe worktree retirement.

  • New Features

    • Added a “Slice” section and ownership checklist to .github/PULL_REQUEST_TEMPLATE.md.
    • Documented branch/PR lifecycle in CONTRIBUTING.md and AGENTS.md.
    • Enforced repo rules: auto-delete merged source branches and protect staging.
  • Migration

    • Start branches from up-to-date origin/staging; declare explicit dependencies as “Depends on #…”.
    • Keep one task per branch; open a draft PR early with scope and known overlaps.
    • Rebase onto origin/staging before review; retire branches after merge/close and use one worktree per branch.

Written for commit d11c9a4. Summary will update on new commits.

Review in cubic

@cursor

cursor Bot commented Aug 2, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@vercel

vercel Bot commented Aug 2, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
dashboard Ready Ready Preview Aug 2, 2026 3:04pm
databuddy-status Ready Ready Preview Aug 2, 2026 3:04pm
documentation Ready Ready Preview Aug 2, 2026 3:04pm

@coderabbitai

coderabbitai Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 69021faf-f5bc-4308-bf39-7f2044c4c797

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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

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

@dosubot

dosubot Bot commented Aug 2, 2026

Copy link
Copy Markdown

📄 Knowledge review

Dosu skipped reviewing this PR because your organization has used its 200 included credits for the month. Your usage will reset on 2026-09-01. To have Dosu review this PR before then, ask your organization admin to upgrade to a pro account.


Leave Feedback Ask Dosu about Databuddy Add Dosu to your team

@greptile-apps

greptile-apps Bot commented Aug 2, 2026

Copy link
Copy Markdown
Contributor

Greptile Summary

This PR documents a short-lived, one-slice branch lifecycle for contributors and agents.

  • Adds explicit scope, dependency, overlap, and branch-retirement checks to the pull request template.
  • Defines rebase-first integration, early draft PRs, isolated worktrees, and branch retirement in agent guidance.
  • Expands contributor instructions with a concrete branch creation, review, and cleanup workflow.

Confidence Score: 5/5

The documentation-only PR appears safe to merge.

The new guidance is internally consistent across the pull request template, agent instructions, and contributor workflow, and it aligns with the repository’s staging-oriented automation.

Important Files Changed

Filename Overview
.github/PULL_REQUEST_TEMPLATE.md Adds slice metadata and checklist items that consistently reinforce the documented branch lifecycle.
AGENTS.md Replaces the brief staging-target instruction with coherent branch ownership, integration, isolation, and retirement guidance.
CONTRIBUTING.md Expands the development workflow into a consistent staging-based branch and PR lifecycle with rebase-first integration.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  A[Update staging] --> B[Create fresh task branch]
  B --> C[Implement one reviewable slice]
  C --> D[Push and open draft PR]
  D --> E[Rebase onto origin/staging]
  E --> F[Run relevant checks]
  F --> G[Review and merge or close]
  G --> H[Delete branch and remove worktree]
Loading

Reviews (1): Last reviewed commit: "docs(repo): define branch lifecycle" | Re-trigger Greptile

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