Two multi-project bugs that caused GRM post-merge workflow failures:
validate_commit_msg.py: Hardcoded DEVX-N prefix → now uses TASK_PREFIX from config.py (configurable via DEVX_TASK_PREFIX env var)
sync_wiki.py: DOCS_DIR was relative to __file__ (package installation path) → now relative to CWD (repo root)
Root Cause
These bugs were introduced by the strict error handling changes in v0.4.2 (PR #17). The strict validation correctly raised errors, but the underlying logic was broken for consumer projects:
GRM commits with GRM-N: prefix were rejected because the validator expected DEVX-N:
mapping.json was looked up in .venv/lib/python3.12/docs/ instead of ./docs/
Tests
Added 3 tests for custom prefix validation (GRM prefix scenario). All 825 tests pass, 100% coverage.
Closes DEVX-9
## Summary
Two multi-project bugs that caused GRM post-merge workflow failures:
1. **validate_commit_msg.py**: Hardcoded `DEVX-N` prefix → now uses `TASK_PREFIX` from config.py (configurable via `DEVX_TASK_PREFIX` env var)
2. **sync_wiki.py**: `DOCS_DIR` was relative to `__file__` (package installation path) → now relative to CWD (repo root)
### Root Cause
These bugs were introduced by the strict error handling changes in v0.4.2 (PR #17). The strict validation correctly raised errors, but the underlying logic was broken for consumer projects:
- GRM commits with `GRM-N:` prefix were rejected because the validator expected `DEVX-N:`
- `mapping.json` was looked up in `.venv/lib/python3.12/docs/` instead of `./docs/`
### Tests
Added 3 tests for custom prefix validation (GRM prefix scenario). All 825 tests pass, 100% coverage.
Closes DEVX-9
Documentation: WARNING — source files changed but no docs updated
Tests: OK
Commit conventions: OK
No issues found by automated checks.
Auto-merge: If all CI checks pass, this PR will be merged automatically.
## Automated PR Review
- Architecture compliance: OK
- Best practices: OK
- Security: OK
- i18n: OK
- Resource management: OK
- Documentation: WARNING — source files changed but no docs updated
- Tests: OK
- Commit conventions: OK
No issues found by automated checks.
---
**Auto-merge:** If all CI checks pass, this PR will be merged automatically.
emil
merged commit 4efac484d0 into master2026-06-22 21:44:35 +00:00
emil
deleted branch DEVX-9-fix-prefix-docsdir2026-06-22 21:44:36 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
emil
Summary
Two multi-project bugs that caused GRM post-merge workflow failures:
DEVX-Nprefix → now usesTASK_PREFIXfrom config.py (configurable viaDEVX_TASK_PREFIXenv var)DOCS_DIRwas relative to__file__(package installation path) → now relative to CWD (repo root)Root Cause
These bugs were introduced by the strict error handling changes in v0.4.2 (PR #17). The strict validation correctly raised errors, but the underlying logic was broken for consumer projects:
GRM-N:prefix were rejected because the validator expectedDEVX-N:mapping.jsonwas looked up in.venv/lib/python3.12/docs/instead of./docs/Tests
Added 3 tests for custom prefix validation (GRM prefix scenario). All 825 tests pass, 100% coverage.
Closes DEVX-9
Automated PR Review
No issues found by automated checks.
Auto-merge: If all CI checks pass, this PR will be merged automatically.