Add pre-commit hooks to awm-v1-0-4 #1

New issue

Closed

opened 2026-06-04 00:37:00 +00:00 by Mark · 1 comment

Mark commented

2026-06-04 00:37:00 +00:00

Owner

Repository awm-v1-0-4 does not have pre-commit hooks configured. Evaluate the repo's language/tooling and add appropriate hooks (.pre-commit-config.yaml for Python, lefthook.yml for Node, or .githooks/pre-commit for simpler repos).

Repository `awm-v1-0-4` does not have pre-commit hooks configured. Evaluate the repo's language/tooling and add appropriate hooks (`.pre-commit-config.yaml` for Python, `lefthook.yml` for Node, or `.githooks/pre-commit` for simpler repos).

Mark added the

enhancement

label

2026-06-04 00:37:51 +00:00

Mark added the

blocked:needs-decision

label

2026-06-07 03:01:38 +00:00

Mark commented

2026-06-07 03:01:38 +00:00

Author

Owner

⏸ Needs Decision

What needs to be decided?

Is this issue still relevant? If yes, remove the blocked:needs-decision label to route back to triage.

Blocking factors:

Didn't meet auto-approve criteria — scope=small, risk=low, spec=partial

Scope: small Risk: low Spec: partial Type: chore
Summary: Add pre-commit hook configuration to the AWM v1.0.4 repository for basic pre-commit quality checks.
Suggestion: Add .pre-commit-config.yaml with universal hooks (trailing-whitespace, end-of-file-fixer, check-yaml, check-added-large-files) since the repo currently has no source code to lint. The language/tooling-agnostic hooks apply immediately; language-specific hooks (ruff/flake8 for Python or eslint/prettier for JS) can be added when actual code lands.
Rationale: The repo is an archived snapshot with only a README.md and no source files, making this a trivially small and low-risk addition. There is no existing AGENTS.md or milestone to align with. A generic pre-commit config with universal hooks is the right baseline — it establishes the infrastructure without assuming a language stack that doesn't yet exist.

To unblock: Remove the blocked:needs-decision label. The triage will apply the appropriate outcome based on your choice above.

## ⏸ Needs Decision **What needs to be decided?** - **Is this issue still relevant?** If yes, remove the `blocked:needs-decision` label to route back to triage. **Blocking factors:** - **Didn't meet auto-approve criteria** — scope=small, risk=low, spec=partial --- **Scope:** small **Risk:** low **Spec:** partial **Type:** chore **Summary:** Add pre-commit hook configuration to the AWM v1.0.4 repository for basic pre-commit quality checks. **Suggestion:** Add `.pre-commit-config.yaml` with universal hooks (trailing-whitespace, end-of-file-fixer, check-yaml, check-added-large-files) since the repo currently has no source code to lint. The language/tooling-agnostic hooks apply immediately; language-specific hooks (ruff/flake8 for Python or eslint/prettier for JS) can be added when actual code lands. **Rationale:** The repo is an archived snapshot with only a README.md and no source files, making this a trivially small and low-risk addition. There is no existing AGENTS.md or milestone to align with. A generic pre-commit config with universal hooks is the right baseline — it establishes the infrastructure without assuming a language stack that doesn't yet exist. **To unblock:** Remove the `blocked:needs-decision` label. The triage will apply the appropriate outcome based on your choice above.

Mark added

quickfix

and removed

enhancement

blocked:needs-decision

labels

2026-07-27 16:31:09 +00:00

Mark added the

triage-approved

label

2026-09-14 13:57:40 +00:00

Mark