Adopt the AI-native SDLC playbook and repository policies

オープン
  • 何か問題がありますか？
#1,192 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@goanpeca がすでに取り組んでいます。

2026年10月28日 から。

  • #1193 @goanpeca による — オープン

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
25/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
github-actions, python
領域
cli, devops, tooling

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.
主要言語
Python
スター
638
フォーク
138
平均マージ
8時間 27分
マージ済み PR（30日）
8

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Backblaze/B2_Command_Line_Tool のほかの issue

Backblaze/B2_Command_Line_Tool の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。