Skip to content

chore(plans): move SVG generation to pre-commit hook#14249

Open
fruch wants to merge 1 commit intoscylladb:masterfrom
fruch:chore/progress-svg-precommit
Open

chore(plans): move SVG generation to pre-commit hook#14249
fruch wants to merge 1 commit intoscylladb:masterfrom
fruch:chore/progress-svg-precommit

Conversation

@fruch
Copy link
Copy Markdown
Contributor

@fruch fruch commented Mar 30, 2026

Summary

Test plan

  • uv run sct.py pre-commit passes (hooks ran successfully during commit)
  • Modify progress.json, run git commit — verify SVG is auto-regenerated
  • Verify no GitHub Action runs on push to master for progress.json changes

🤖 Generated with Claude Code

@fruch fruch force-pushed the chore/progress-svg-precommit branch from fff24fb to b8e8190 Compare March 30, 2026 11:00
@scylladb-promoter
Copy link
Copy Markdown
Collaborator

scylladb-promoter commented Mar 30, 2026

✅ Test Summary: PASSED

✅ Precommit: PASSED

Total Passed Failed Skipped
26 15 0 11

✅ Tests: PASSED

Total Passed Failed Errors Skipped
1705 1690 0 0 15

Full build log

@fruch fruch added the backport/none Backport is not required label Mar 30, 2026
Replace the GitHub Actions workflow for regenerating the progress SVG
with a pre-commit hook, since the action lacks push permissions.
Fix SVG generator to include trailing newline for end-of-file-fixer
compatibility. Update progress.json and MASTER.md to reflect merged
PRs (scylladb#13916, scylladb#13887, scylladb#13877, scylladb#13769, scylladb#13629).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@fruch fruch force-pushed the chore/progress-svg-precommit branch from b8e8190 to c9c179f Compare March 30, 2026 11:23
@fruch fruch added P2 High Priority plans PRs that add or modify implementation plans labels Mar 30, 2026
@fruch fruch requested a review from a team March 30, 2026 12:11
@soyacz
Copy link
Copy Markdown
Contributor

soyacz commented Mar 30, 2026

will this be adding .svg automatically to the commits?
maybe better to add this to PR's description? I'm not convinced to add svg's to the repo on each update - will increase size too much after some time

@fruch
Copy link
Copy Markdown
Contributor Author

fruch commented Mar 30, 2026

will this be adding .svg automatically to the commits?
maybe better to add this to PR's description? I'm not convinced to add svg's to the repo on each update - will increase size too much after some time

It's text...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ai-assisted backport/none Backport is not required P2 High Priority plans PRs that add or modify implementation plans

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants