openhaven/openhaven.net
1
0
Fork 0
Code Issues Pull requests 8 Projects Releases Packages Wiki Activity Actions 121

chore(bmad): gitignore BMAD 6.9.0 installer files + local tooling #13

Open
zach wants to merge 1 commit from zachmiltz/bmad-690-gitignore-housekeeping into main
pull from: zachmiltz/bmad-690-gitignore-housekeeping
merge into: openhaven:main
Conversation 0 Commits 1 Files changed 5 +44 -15
zach commented 2026-07-02 14:18:55 +00:00
Collaborator
Copy link

Housekeeping after the BMAD 6.0.3 → 6.9.0 upgrade (2026-06-26) reorganized _bmad/ and left installer-managed / personal files leaking into git status. No code or site-build (src/) changes.

Ignored (regenerate via npx bmad-method install; the _bmad/config.toml / config.user.toml headers self-declare installer-managed & personal):

  • _bmad/config.toml, _bmad/config.user.toml, _bmad/scripts/, _bmad/_config/skill-manifest.csv
  • .agents/ (oh-my-claudecode scaffolding), .mcp.json (per-developer MCP config — just the linear-oh URL, no secrets)

Tracked (genuine team config):

  • _bmad/custom/config.toml — team overrides; the file says "Committed to the repo — applies to every developer."
  • _bmad/custom/.gitignore — ignores *.user.toml

Committed the installer's 6.9.0 regeneration of already-tracked _bmad/_config/manifest.yaml + _bmad/bgw/config.yaml.

Two judgment calls to sanity-check

  1. _bmad/scripts/ (the resolve_*.py resolvers the skills call) is ignored as installer-regenerable — flip to tracked if you'd rather nobody has to reinstall to get them.
  2. _bmad/_config/manifest.yaml + _bmad/bgw/config.yaml are kept tracked (they already were) — could be un-tracked too if we want all installer output ignored. Left minimal here.

🤖 Generated with Claude Code

Housekeeping after the **BMAD 6.0.3 → 6.9.0** upgrade (2026-06-26) reorganized `_bmad/` and left installer-managed / personal files leaking into `git status`. **No code or site-build (`src/`) changes.** **Ignored** (regenerate via `npx bmad-method install`; the `_bmad/config.toml` / `config.user.toml` headers self-declare installer-managed & personal): - `_bmad/config.toml`, `_bmad/config.user.toml`, `_bmad/scripts/`, `_bmad/_config/skill-manifest.csv` - `.agents/` (oh-my-claudecode scaffolding), `.mcp.json` (per-developer MCP config — just the `linear-oh` URL, no secrets) **Tracked** (genuine team config): - `_bmad/custom/config.toml` — team overrides; the file says *"Committed to the repo — applies to every developer."* - `_bmad/custom/.gitignore` — ignores `*.user.toml` **Committed** the installer's 6.9.0 regeneration of already-tracked `_bmad/_config/manifest.yaml` + `_bmad/bgw/config.yaml`. ### Two judgment calls to sanity-check 1. `_bmad/scripts/` (the `resolve_*.py` resolvers the skills call) is **ignored** as installer-regenerable — flip to tracked if you'd rather nobody has to reinstall to get them. 2. `_bmad/_config/manifest.yaml` + `_bmad/bgw/config.yaml` are **kept tracked** (they already were) — could be un-tracked too if we want all installer output ignored. Left minimal here. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
BMAD was upgraded 6.0.3 -> 6.9.0 (2026-06-26), which reorganized _bmad/ and
left several installer-managed / personal files leaking as untracked. Ignore
those (they regenerate via `npx bmad-method install`) so the working tree stays
clean; track only genuine team customization.

- .gitignore: ignore _bmad/config.toml, _bmad/config.user.toml, _bmad/scripts/,
  _bmad/_config/skill-manifest.csv (installer-managed / personal), plus .agents/
  and .mcp.json (oh-my-claudecode scaffolding + per-developer MCP config).
- Track _bmad/custom/config.toml (team overrides — the file self-declares
  "committed to the repo") and _bmad/custom/.gitignore (ignores *.user.toml).
- Commit the installer's 6.9.0 regeneration of the already-tracked
  _bmad/_config/manifest.yaml and _bmad/bgw/config.yaml.

No code or site-build (src/) changes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This pull request has changes conflicting with the target branch.
  • .gitignore
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin zachmiltz/bmad-690-gitignore-housekeeping:zachmiltz/bmad-690-gitignore-housekeeping
git switch zachmiltz/bmad-690-gitignore-housekeeping

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff zachmiltz/bmad-690-gitignore-housekeeping
git switch zachmiltz/bmad-690-gitignore-housekeeping
git rebase main
git switch main
git merge --ff-only zachmiltz/bmad-690-gitignore-housekeeping
git switch zachmiltz/bmad-690-gitignore-housekeeping
git rebase main
git switch main
git merge --no-ff zachmiltz/bmad-690-gitignore-housekeeping
git switch main
git merge --squash zachmiltz/bmad-690-gitignore-housekeeping
git switch main
git merge --ff-only zachmiltz/bmad-690-gitignore-housekeeping
git switch main
git merge zachmiltz/bmad-690-gitignore-housekeeping
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
openhaven/openhaven.net!13
No description provided.