Skip to content

docs: add tieguy to advisors and mentors#621

Closed
castrojo wants to merge 12 commits intoprojectbluefin:mainfrom
castrojo:feature/add-tieguy-mentor
Closed

docs: add tieguy to advisors and mentors#621
castrojo wants to merge 12 commits intoprojectbluefin:mainfrom
castrojo:feature/add-tieguy-mentor

Conversation

@castrojo
Copy link
Contributor

@castrojo castrojo commented Feb 7, 2026

Adds @tieguy to the Advisors and Mentors section of the contributors page.

Changes

  • Added GitHubProfileCard for tieguy in the mentors section
  • Profile data will be auto-fetched at build time

Testing

Verified locally with dev server at http://localhost:3000/donations/contributors

Add comprehensive fork workflow documentation to AGENTS.md:
- Configure castrojo/documentation as origin (working fork)
- Configure projectbluefin/documentation as upstream
- Document daily development workflow in fork
- Document PR submission process with squashing and browser-based submission
- Document upstream sync process
- Explain rationale for fork-based workflow

This workflow ensures clean PR history and gives user control over
PR title/description while maintaining independent fork for experimentation.

Assisted-by: Claude Sonnet 4.5 via GitHub Copilot
Add missing export-state/ pattern to prevent tracking temporary merge
artifacts. This was fixed via 'bd doctor --fix'.
Set sync-branch to 'beads-metadata' to isolate beads commits from
feature branches. This ensures PRs to upstream contain only code changes.
Add .beads/ to root .gitignore to prevent accidental commits of beads
metadata on feature branches. Beads metadata is managed exclusively on
the beads-metadata sync branch.

This ensures clean PRs to upstream (projectbluefin/documentation) that
contain only code changes without issue tracking metadata.
Update AGENTS.md to document the beads sync branch strategy:
- Add 'Sync Branch Workflow' subsection explaining branch isolation
- Update git workflow exceptions for beads metadata
- Clarify that beads commits go to beads-metadata branch automatically
- Document daily workflow for feature branches + beads tracking

This ensures AI agents understand the fork-specific workflow where:
- Code changes: feature branches → clean PRs to upstream
- Beads metadata: beads-metadata branch → stays in fork

Assisted-by: Claude Sonnet 4.5 via GitHub Copilot
All actionable items from .planning-archive/ have been migrated to beads
issue tracking system. The archive contained only historical documentation
from completed v1.0 and v1.1 milestones.

Migration verification:
- Node.js upgrade: bluefin-docs-k89 (closed)
- Homebrew tap promotion: bluefin-docs-itu (closed)
- Community engagement: bluefin-docs-e33 (open)
- All phase work, quick tasks, and todos accounted for

Updated AGENTS.md to remove references to the now-deleted archive.

Migration completed: 2026-01-31 (as documented in former MIGRATION.md)
Final cleanup: 2026-02-02

Assisted-by: Claude Sonnet 4.5 via GitHub Copilot
- Delete .github/COPILOT_SETUP.md (referenced wrong package manager)
- Fix AGENTS.md line 1160 (remove outdated .planning reference)
- Update 'Landing the Plane' section to clarify fork workflow requirements
- Update README.md to correct npm reference (was incorrectly mentioning bun)
- Add .beads/PRIME.md with custom context for fork + sync branch workflow

All changes ensure documentation accurately reflects:
- npm as the standard package manager (not bun)
- Feature branch + PR workflow (never push directly to main)
- Fork setup (castrojo/documentation → projectbluefin/documentation)

The PRIME.md file provides automatic context recovery for AI agents after
compaction, preventing agents from forgetting critical workflow rules like
'always use feature branches' and 'never use TodoWrite'.

Assisted-by: Claude Sonnet 4.5 via GitHub Copilot
Fork (castrojo/documentation) maintains beads configuration for issue tracking.
Upstream (projectbluefin/documentation) remains pristine without beads.

Resolved conflicts:
- .gitignore: Use selective beads patterns (ignore runtime, allow issues.jsonl)
- AGENTS.md: Keep fork's workflow documentation
- .beads/: Maintain fork's beads configuration files
Add detailed beads documentation to AGENTS.md covering:
- What is beads and why we use it (git-native, distributed, CLI-first)
- Data model and storage strategy (SQLite + JSONL + sync branch workflow)
- Core concepts (issues, priorities, status lifecycle, dependencies)
- Complete command reference table with all beads commands
- Three-branch model (main, feature/*, beads-metadata) with ASCII diagrams
- Sync branch workflow and when to use each command
- Common sync scenarios with step-by-step examples
- Agent-specific patterns (bulk creation, dependency chains, batch closure)
- Troubleshooting guide for common beads issues
- Best practices and critical guidelines for agents
- Integration with landing the plane session close protocol

Target audience: AI agents new to beads working on this repository.
Visual style: Agent-efficient (tables, ASCII, structured text).

Resolves: bluefin-docs-5le

Assisted-by: Claude Sonnet 4.5 via GitHub Copilot
Expand the Fork Workflow section with detailed guidance on:
- What changes go upstream vs stay in fork
- Decision tree for PR submission
- Why beads stays isolated (upstream doesn't use it)
- Visual diagram of fork relationship
- Complete submission process with validation steps

This completes the beads documentation work by making it crystal clear
when to submit PRs to projectbluefin/documentation (documentation
improvements) vs when to keep changes in castrojo/documentation (beads
and internal tracking).

Assisted-by: Claude Sonnet 4.5 via GitHub Copilot
Add tieguy to the Advisors and Mentors section of the contributors page.

Assisted-by: Claude Sonnet 4.5 via GitHub Copilot
@castrojo
Copy link
Contributor Author

castrojo commented Feb 7, 2026

Closing to remove beads metadata that should not be in upstream PRs. Will reopen with clean commit.

@castrojo castrojo closed this Feb 7, 2026
castrojo added a commit to castrojo/documentation that referenced this pull request Feb 7, 2026
… leaks

Add critical instructions for creating upstream PRs:
- MUST branch from upstream/main (not origin/main) to avoid beads files
- Use --no-verify flag to skip beads hooks on upstream branches
- Verify PR contains only intended files before submission

This prevents beads metadata from appearing in PRs to projectbluefin/documentation.

Context: PR projectbluefin#621 accidentally included .beads/ files because it branched from
origin/main. PR projectbluefin#622 is clean because it branched from upstream/main.

Assisted-by: Claude Sonnet 4.5 via GitHub Copilot
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