Skip to content

docs: remove duplicate Project initiative #1963

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
codeforester merged 1 commit into from
Aug 17, 2026
Merged

docs: remove duplicate Project initiative #1963

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion .github/ISSUE_TEMPLATE/implementation.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,6 @@ body:
description: Select the intended Base Project Initiative field value.
options:
- BanyanLabs Dogfood
- BanyanLabs Dogfooding
- Workspace Handling
- pyproject/uv
- v1.0 Readiness
Expand Down
1 change: 0 additions & 1 deletion .github/base-project.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,6 @@ project:
- Product
initiatives:
- BanyanLabs Dogfood
- BanyanLabs Dogfooding
- Workspace Handling
- pyproject/uv
- v1.0 Readiness
Expand Down
17 changes: 9 additions & 8 deletions docs/github-workflow.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -110,12 +110,11 @@ Project fields:

- `Status`: `Triage`, `Backlog`, `Ready`, `In Progress`, `In Review`, `Done`
- `Priority`: `P0`, `P1`, `P2`, `P3`
- `Area`: `CLI`, `Setup`, `Workspace`, `Manifest`, `Runtime`, `Shell`,
`Python`, `Docs`, `CI`, `Packaging`, `Security`, `Product`
- `Area`: repo-specific options declared in
[`.github/base-project.yml`](../.github/base-project.yml)
- `Size`: `T`, `S`, `M`, `L`
- `Initiative`: `BanyanLabs Dogfood`, `BanyanLabs Dogfooding`,
`Workspace Handling`, `pyproject/uv`, `v1.0 Readiness`, `Adoption Polish`,
`Contract Hardening`, `Agentic Coding Platform`
- `Initiative`: repo-specific options declared in
[`.github/base-project.yml`](../.github/base-project.yml)

Use `Agentic Coding Platform` for work that makes GitHub-centered agentic
implementation more repeatable: agent-ready repo baselines, agent-readiness
Expand Down Expand Up @@ -740,13 +739,15 @@ Recommended fields:

- `Status`: Triage, Backlog, Ready, In Progress, In Review, Done
- `Priority`: P0, P1, P2, P3
- `Area`: repo-specific options declared in `.github/base-project.yml`
- `Area` and `Initiative`: repo-specific options declared in
[`.github/base-project.yml`](../.github/base-project.yml)
- `Size`: T, S, M, L
- `Initiative`: repo-specific options declared in `.github/base-project.yml`

Keep `Status`, `Priority`, and `Size` standardized across repos. Keep `Area`
and `Initiative` repo-specific, and let `basectl repo configure` add missing
options additively from the repo config file.
options additively from the repo config file. The metadata vocabulary above and
the repository configuration are the source of truth; do not maintain a second
concrete option list in this workflow guide.

Useful views:

Expand Down
2 changes: 1 addition & 1 deletion docs/repo-baseline.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -481,7 +481,7 @@ the repo Project:
- `Area`: `CLI`, `Setup`, `Workspace`, `Manifest`, `Runtime`, `Shell`,
`Python`, `Docs`, `CI`, `Packaging`, `Security`, `Product`
- `Size`: `T`, `S`, `M`, `L`
- `Initiative`: `BanyanLabs Dogfood`, `BanyanLabs Dogfooding`,
- `Initiative`: `BanyanLabs Dogfood`,
`Workspace Handling`, `pyproject/uv`, `v1.0 Readiness`, `Adoption Polish`,
`Contract Hardening`, `Agentic Coding Platform`, plus values passed with
`--initiative-option`
Expand Down
Loading