Repository navigation
Open
Description
Problem
The basefoundry/.github repository has GitHub Issues disabled, but it can still contain open pull requests whose titles follow the old category-prefix convention. Track its migration from the Base repository and do not enable Issues as a side effect.
Expected behavior
After the accepted templates and organization-config adoption are active, inventory every open PR in basefoundry/.github and rename it to plain outcome/problem wording. Closed and merged PR titles remain historical. If no open PR exists, record that evidence and close this task with a reasoned no-op.
Scope and non-goals
Scope: Metadata-only title migration for open PRs in basefoundry/.github.
Non-goals: Do not enable repository Issues, create an issue in .github, change branch policy, or edit closed/merged titles.
Affected areas
- Open pull request titles in
basefoundry/.github. - Base tracker: Track implementation of the accepted Base governance plan #2665.
- Accepted source: Revise the Base ecosystem governance design and implementation plan #2664.
Impact and evidence
- Product intent: No product behavior change.
- Architecture and contracts: Applies the accepted title rule to the special org-config profile.
- User guidance: No user content change; inventory open PRs.
- CLI/API and reference: No CLI change.
- Operations and safety: Keep Issues disabled and preserve org-level settings.
- Validation and testing: Read back each changed PR title and compare counts.
- Examples and downstream use: No examples affected; no source examples in this metadata-only task.
- Governance and contributor process: Apply the shared plain-title contract through a repo-local PR linked to this Base issue.
- Decision records: No new decision.
- Release notes: Reasoned
none; metadata-only change.
Open questions
- Confirm templates and title rules are live before execution; ambiguous titles remain unchanged and get separate clarification issues.
Plan
- S1: One PR in
basefoundry/.github, linking this issue by full URL because Issues are disabled in the target repo. - Dependencies: Base issue form Use one issue form and a reviewed Ready checklist #2667, PR template Define the pull request template and documentation-impact contract #2669, and
.githubadoption Adopt the governance profile in the organization configuration repository #2685. - Acceptance criteria:
- Inventory all open PRs at execution time; no issue inventory is expected because Issues are disabled.
- Rename all clear category-prefixed titles to plain outcome/problem wording; record before/after counts and mapping.
- Leave ambiguous titles unchanged and leave closed/merged PRs untouched.
- Keep the
.githubIssues-disabled setting unchanged.
- Validation: Read back PR titles and inspect the repository setting; compare inventory counts.
- Risks and rollback: Org-level templates affect many repos; preserve title mapping and restore any incorrect title exactly.
- Decision impact: No new decision is accepted.
Metadata
Metadata
Assignees
Labels
documentationDocumentation improvementsDocumentation improvements
Type
Projects
- StatusShow more project fieldsBacklog
Activity
codeforester commentedon Nov 11, 2026
Pre-Triage review against the accepted plan (#2664, tracker #2665)
basefoundry/.githubhas 0 open PRs today, so unless that changes, this closes as the no-op it describes. The decision is still taken at execution time, as written.Claude Code (Opus 5.5), reviewing from Ramesh's account at his request. This review comes before Triage, so it is not an issue-loop round.
Replace the governance implementation plan with the staged release pl…