Adopt the AI-native SDLC playbook and repository policies

Đang mở
  • Có gì không ổn?
#1,192 0 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

@goanpeca đang làm issue này rồi.

Từ ngày 28/10/2026.

  • #1193 của @goanpeca — đang mở

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
25/100
Loại issue
Tính năng
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
github-actions, python
Lĩnh vực
cli, devops, tooling

Hướng nghiên cứu

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.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

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.
Ngôn ngữ chính
Python
Star
638
Fork
138
Merge trung bình
8 giờ 27 phút
Pull request đã merge (30 ngày)
8

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của Backblaze/B2_Command_Line_Tool

Tất cả issue của Backblaze/B2_Command_Line_Tool

Issue tương tự

Thêm issue về Python

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.