Commit Graph

8 Commits

Author SHA1 Message Date
didericis 50f5b3aa7f ci(badges): add coverage percentage to quality badges
test / integration (pull_request) Successful in 16s
test / unit (pull_request) Successful in 43s
test / unit (push) Successful in 44s
lint / lint (push) Successful in 1m49s
test / integration (push) Successful in 18s
Update Quality Badges / update-badges (push) Successful in 1m53s
The update-badges workflow only refreshed pylint and pyright. Add a
coverage step that runs the unit suite under coverage.py, extracts the
TOTAL percentage, and updates a new coverage badge in the README.
Also trigger the workflow on .coveragerc changes.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NkwFXLFff9PYPy4wgVBJp9
2026-06-25 15:13:44 -04:00
didericis a7de3dbb9f fix(ci): fix badge sed patterns and pylint score URL encoding
The old patterns required a trailing ] that badge markdown doesn't have,
so sed never matched and the README was never updated. Switch to matching
only the /badge/tool-... URL segment, which is stable and unambiguous.
Also encode / as %2F in the pylint score for a valid shields.io URL.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-06 00:48:54 -04:00
didericis 436f42c00c fix(ci): fix pylint/pyright output capture and parsing
test / unit (push) Successful in 38s
test / integration (push) Successful in 52s
- Capture full output with || true instead of pipefail-sensitive | tail -1
- Use lookbehind for pylint score to avoid matching "previous run" value
- Use lookahead for pyright error count to search full output not just last line
- Remove hardcoded fallback values that masked parse failures

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-06 00:40:05 -04:00
didericis 881869352d fix(ci): continue update-badges job on pylint/pyright errors
test / unit (push) Successful in 38s
test / integration (push) Successful in 56s
Badges should reflect the current score even when there are lint/type
errors, not abort the job entirely.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-06 00:32:26 -04:00
didericis 3f982009e2 fix(ci): fix YAML parse error in update-badges workflow
test / unit (push) Successful in 34s
test / integration (push) Successful in 53s
Zero-indented lines in the commit message body broke the block scalar,
preventing Gitea from parsing the file at all.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-06 00:17:06 -04:00
didericis 544a024e22 ci: add update-badges workflow with dispatch trigger
- Runs on push to main when Python files change
- Can be manually triggered via workflow_dispatch
- Executes pylint and pyright to extract quality scores
- Updates README.md badges with current metrics
- Auto-commits changes with [skip ci] to prevent loops

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
2026-06-04 12:33:11 -04:00
didericis a5d08bd64e fix: remove pip caching from Gitea workflows to fix ETIMEDOUT errors
Lint and Type Check / lint (push) Successful in 1m26s
test / unit (pull_request) Successful in 36s
test / integration (pull_request) Failing after 45s
The Gitea Actions runner doesn't have access to pip cache storage,
causing 'reserveCache failed: connect ETIMEDOUT' errors.

Removed cache configuration from both:
- .gitea/workflows/lint.yml
- .gitea/workflows/update-badges.yml

Pip will download dependencies fresh on each run, which is acceptable
for CI workflows and avoids the timeout errors.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
2026-06-04 12:01:28 -04:00
didericis e1ec0afd86 ci: add workflow to auto-update quality badges on main
Created update-badges.yml Gitea Actions workflow that:
- Runs on push to main when Python files change
- Executes pylint and pyright
- Extracts quality scores from tool output
- Updates README.md badges with current scores
- Auto-commits changes with [skip ci] to avoid loop

This keeps the quality badges in README.md in sync with
actual code quality metrics automatically.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
2026-06-04 11:58:01 -04:00