groovescript/GrooveScript Chart Action

Compile .gs drum charts to PDF on pull requests

Trust Signals

name	description	required	default
groovescript-version	Git ref (tag, branch, or SHA) of groovescript/groovescript to install. Default "latest" tracks the default branch HEAD of groovescript/groovescript. Pin a tag or SHA for reproducibility.	no	latest
lilypond-version	LilyPond version to install (e.g. "2.24.3").	no	2.24.3
paths	Newline-separated glob(s) of .gs files to consider. Default: every .gs in the repo.	no	*/.gs
only-changed	If "true" (default), compile only .gs files changed in the PR relative to the base branch. If "false", compile every match of `paths`.	no	true
commit-ly	If "true", stage and commit the intermediate .ly next to the .pdf. If "false" (default), only .pdf is committed.	no	false
commit-message	Commit message prefix for the render commit.	no	Re-render charts
fail-on-error	If "true" (default), the workflow fails when any .gs fails to compile. Already-rendered successful files are NOT committed in that case (all-or-nothing).	no	true
compact	If "true", pass --compact to `groovescript compile` so rendered PDFs use the compact layout. Default "false".	no	false
working-directory	Directory to search for .gs files. Useful when charts live in a subfolder. Default: repo root.	no	.
base-ref	Base ref for diff comparison. Defaults to PR base.	—	${{ github.base_ref }}
head-ref	Head ref to push rendered artifacts to. Defaults to PR head.	—	${{ github.event.pull_request.head.ref }}

no outputs