| Files | Last commit | Last update |
|---|---|---|
docs: add design-decisions record and AGENTS.md (#180) Three review rounds on 2026-09-12 each re-reported decisions (timeout 0 = no limit, the BT.2020 HDR path, speed 0 = unset, the maintainer diary not shipping, colour flags already validated). docs/design-decisions.md lists each with its rationale, the code that holds it and the test that pins it; AGENTS.md, CONTRIBUTING.md, the bug template and the README docs table send a reviewer there before filing. Claude-Session: https://claude.ai/code/session_013tPrsGXLuaGU7t643QNUZs Co-authored-by: Claude <noreply@anthropic.com> | 2 months ago | |
Add Dependabot, CodeQL, PR-labeling, CI concurrency, and more (#130) * Add Dependabot, CodeQL, PR-labeling, PR template, and SECURITY.md Fills in the standard GitHub automation this repo hadn't set up yet: - .github/dependabot.yml: weekly PRs for GitHub Actions pins and npm metadata (no requirements.txt to watch -- scripts/ is stdlib-only). - .github/workflows/codeql.yml: static analysis for Python and the one JS file (bin/install.js), on every PR/push to main plus weekly. This repo has had a real vulnerability of exactly the kind CodeQL targets (batch.py recipe steps resolving outside scripts/ via an absolute path or `../` traversal, fixed in #124). - release-drafter.yml gains an `autolabel` job (pull_request_target: opened/reopened/synchronize) that applies fix/feature/major/chore labels to a PR from its title/changed files via release-drafter's autolabeler, and release-drafter.yml gains the autolabeler rules driving it. This matters beyond the draft release: release.yml's auto version-bump (added in #129) resolves the next version from these same labels, and until now no PR in this repo has ever carried one -- every auto-bump would silently default to patch forever without this. - .github/pull_request_template.md: the Summary/Test-plan shape every recent PR in this repo has already been using by hand. - SECURITY.md: points at GitHub's private vulnerability-reporting flow instead of a public issue. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tPrsGXLuaGU7t643QNUZs * Add CI concurrency cancellation, Dependabot auto-merge, issue templates - ci.yml/codeql.yml: cancel a superseded run on the same PR/branch when a new push arrives instead of letting it finish for nothing -- real savings here since the test matrix includes macOS (10x Ubuntu's minute cost) and Windows (2x). - .github/workflows/dependabot-auto-merge.yml: approves and enables squash auto-merge for Dependabot's own PRs once CI is green, for any update that isn't a semver-major bump (those still wait for a human). Requires "Allow auto-merge" turned on in repo Settings -> General -- this workflow can't flip that setting itself. - .github/ISSUE_TEMPLATE/: bug_report.md, feature_request.md matching this repo's actual triage needs (tool/version, exact command, doctor --json output for FFmpeg-build-specific bugs), plus config.yml routing a security report to SECURITY.md's private flow instead of a public issue. Considered a PR-title-format linter (amannn/action-semantic-pull-request) to backstop release-drafter's title-based autolabeler, but dropped it: that action enforces conventional-commits' `type: subject` colon syntax, and this repo's actual title history ("Fix batch.py...", "Add release- drafter...", "Replace README logo...") never uses colons except by accident ("CI: retry..."). Enforcing it would fail titles in this repo's own established style for no real benefit -- a PR that doesn't match autolabeler's patterns just gets a label added by hand instead, same as before autolabeler existed. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tPrsGXLuaGU7t643QNUZs --------- Co-authored-by: Claude <noreply@anthropic.com> | 2 months ago | |
Add Dependabot, CodeQL, PR-labeling, CI concurrency, and more (#130) * Add Dependabot, CodeQL, PR-labeling, PR template, and SECURITY.md Fills in the standard GitHub automation this repo hadn't set up yet: - .github/dependabot.yml: weekly PRs for GitHub Actions pins and npm metadata (no requirements.txt to watch -- scripts/ is stdlib-only). - .github/workflows/codeql.yml: static analysis for Python and the one JS file (bin/install.js), on every PR/push to main plus weekly. This repo has had a real vulnerability of exactly the kind CodeQL targets (batch.py recipe steps resolving outside scripts/ via an absolute path or `../` traversal, fixed in #124). - release-drafter.yml gains an `autolabel` job (pull_request_target: opened/reopened/synchronize) that applies fix/feature/major/chore labels to a PR from its title/changed files via release-drafter's autolabeler, and release-drafter.yml gains the autolabeler rules driving it. This matters beyond the draft release: release.yml's auto version-bump (added in #129) resolves the next version from these same labels, and until now no PR in this repo has ever carried one -- every auto-bump would silently default to patch forever without this. - .github/pull_request_template.md: the Summary/Test-plan shape every recent PR in this repo has already been using by hand. - SECURITY.md: points at GitHub's private vulnerability-reporting flow instead of a public issue. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tPrsGXLuaGU7t643QNUZs * Add CI concurrency cancellation, Dependabot auto-merge, issue templates - ci.yml/codeql.yml: cancel a superseded run on the same PR/branch when a new push arrives instead of letting it finish for nothing -- real savings here since the test matrix includes macOS (10x Ubuntu's minute cost) and Windows (2x). - .github/workflows/dependabot-auto-merge.yml: approves and enables squash auto-merge for Dependabot's own PRs once CI is green, for any update that isn't a semver-major bump (those still wait for a human). Requires "Allow auto-merge" turned on in repo Settings -> General -- this workflow can't flip that setting itself. - .github/ISSUE_TEMPLATE/: bug_report.md, feature_request.md matching this repo's actual triage needs (tool/version, exact command, doctor --json output for FFmpeg-build-specific bugs), plus config.yml routing a security report to SECURITY.md's private flow instead of a public issue. Considered a PR-title-format linter (amannn/action-semantic-pull-request) to backstop release-drafter's title-based autolabeler, but dropped it: that action enforces conventional-commits' `type: subject` colon syntax, and this repo's actual title history ("Fix batch.py...", "Add release- drafter...", "Replace README logo...") never uses colons except by accident ("CI: retry..."). Enforcing it would fail titles in this repo's own established style for no real benefit -- a PR that doesn't match autolabeler's patterns just gets a label added by hand instead, same as before autolabeler existed. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_013tPrsGXLuaGU7t643QNUZs --------- Co-authored-by: Claude <noreply@anthropic.com> | 2 months ago |
| Files | Last commit | Last update |
|---|---|---|
| 2 months ago | ||
| 2 months ago | ||
| 2 months ago |