Adopt the AI-native SDLC playbook and repository policies

Aperta
  • Qualcosa non va?
#1,192 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@goanpeca ci sta già lavorando.

Dal 28/10/2026.

  • #1193 di @goanpeca — aperta

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github-actions, python
Ambito
cli, devops, tooling

Direzione di ricerca

Start by reading the referenced intent/review-process/intent.md, noxfile.py, ci.yml, and README.release.md, then compare the listed review lessons with the existing repository policies and CI jobs. The work spans contributor guidance, local CI and changelog checks, release and community policies, AI-native planning materials, and a maintainer review proposal; done means these deliverables are implemented and the repo-admin decisions are resolved.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement

Problem

More B2 CLI PRs are now written with coding agents, and the repo gives them nothing to read before they start. Reviewers keep asking for the same things: a changelog.d fragment (#1137, #957, #905), a fragment ending in a full stop (#1044), the right fragment type with internal changes kept out of user sections (#1137, #763), behavior changes such as exit codes called out for script users (#1165), a focused test for every input branch of a fix (#1165, #924), developer-only knobs kept out of the main --help (#1163), and stdout/stderr treated as a contract (--quiet, stderr monitored by users; #924, #1000, #1180). Several PRs were also held up by live-B2 integration flakiness on master that was not the PR's fault (#1062, #1125, #1167).

There is no single local command that mirrors CI (codespell, nox -s lint, the changelog checks, build, unit and integration tests), so contributors find failures after pushing. The release steps live in a two-line README.release.md and in noxfile.py. The repo also lacks the standard policy files: no SECURITY.md, CODE_OF_CONDUCT.md, issue forms or PR template.

Proposed outcome

  • Agents and contributors read the recurring review lessons before they write code (AGENTS.md, with CLAUDE.md pointing to it), and reviewers follow one written process (REVIEW.md).
  • One local command, nox -s ci, that mirrors the CI lint, build and test jobs, plus a local nox -s changelog_check that matches the CI "Validate new changelog entries" step. towncrier stays as the changelog tool.
  • A documented release process (RELEASE.md, replacing README.release.md), a security policy, a code of conduct, issue forms and a PR template.
  • Larger changes start from intent/<slug>/intent.md → spec.md → plan.md, following the AI-native SDLC playbook, with the playbook skills in .claude/skills/ and a ruff format hook for Claude Code edits.
  • A proposal, for the maintainers to decide, on scaling human review by risk (tiers by path, re-approval on new commits, required conversation resolution, automated AI and security review, merge queue, reviewer evals, metrics).

No CLI behavior changes.

Settings that need a repo admin

  • Enable private vulnerability reporting (needed by SECURITY.md and the issue form's security link).
  • Decide whether to add a .github/CODEOWNERS file, and who is in it.
  • Confirm which branch protection is applied to master.
  • Decide whether Dependabot PRs should keep running the full CI matrix (live-B2 secrets) or be gated.
  • Fix the codespell step in ci.yml: ignore_words_list: datas re-use is space-separated, so the action passes re-use as the path to check and codespell checks nothing. Use datas,re-use and fix the existing typos it then finds.
  • Review intent/review-process/intent.md and accept, reshape or close it.
Lingua principale
Python
Stelle
638
Fork
138
Merge medio
8h 27m
PR unite (30g)
8

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Backblaze/B2_Command_Line_Tool

Tutte le issue di Backblaze/B2_Command_Line_Tool

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.