GitHub Actions: moved the action.yml files to validate/ and acceptance/ at the repo root for shorter references

Author: drowaudio

.github/actions/README.md

@@ -1,6 +1,8 @@
 # pluginval GitHub Actions
 
 Two composite actions for using pluginval from another repository's workflows.
+Their `action.yml` files are in `validate/` and `acceptance/` at the repository
+root, which keeps the references short; the scripts they run are in this directory.
 Both run on Linux, macOS and Windows runners, download the matching pluginval
 release (or use a binary you give them), run everything they are given and fail
 the step if anything failed.
@@ -18,7 +20,7 @@ On Linux the plugin is run under `xvfb-run` when there is no `DISPLAY` (install
 Validates one or more plugins.
 
 ```yaml
-- uses: Tracktion/pluginval/.github/actions/validate@v2
+- uses: Tracktion/pluginval/validate@v2
   with:
     plugins: |
       build/MyPlugin_artefacts/Release/VST3/MyPlugin.vst3
@@ -47,7 +49,7 @@ Runs the [acceptance tests](../../docs/Acceptance%20testing.md) for every config
 plugin.
 
 ```yaml
-- uses: Tracktion/pluginval/.github/actions/acceptance@v2
+- uses: Tracktion/pluginval/acceptance@v2
   with:
     config-dir: tests/acceptance
     plugin: build/MyPlugin_artefacts/Release/VST3/MyPlugin.vst3
@@ -85,7 +87,7 @@ Both actions set:
 To keep the reports and diffs from a failed run:
 
 ```yaml
-- uses: Tracktion/pluginval/.github/actions/acceptance@v2
+- uses: Tracktion/pluginval/acceptance@v2
   id: acceptance
   with:
     config-dir: tests/acceptance
@@ -116,7 +118,7 @@ jobs:
     steps:
       # ... build the plugin ...
 
-      - uses: Tracktion/pluginval/.github/actions/validate@v2
+      - uses: Tracktion/pluginval/validate@v2
         with:
           plugins: build/MyPlugin_artefacts/Release/VST3/MyPlugin.vst3
           report-dir: pluginval-reports

.github/workflows/acceptance.yml

@@ -69,7 +69,7 @@ jobs:
         working-directory: build
         run: ctest -C Release --output-on-failure -R pluginval.acceptance
 
-      # The reusable actions in .github/actions, run against the build above
+      # The reusable actions (validate/ and acceptance/), run against the build above
       # (pluginval-path) rather than a downloaded release.
       - name: Prepare action fixtures
         id: fixtures
@@ -100,7 +100,7 @@ jobs:
 
       - name: "Action: validate"
         id: validate
-        uses: ./.github/actions/validate
+        uses: ./validate
         with:
           pluginval-path: ${{ steps.fixtures.outputs.pluginval }}
           args: --skip-gui-tests
@@ -109,7 +109,7 @@ jobs:
       - name: "Action: validate (missing plugin, expected to fail)"
         id: validate-missing
         continue-on-error: true
-        uses: ./.github/actions/validate
+        uses: ./validate
         with:
           pluginval-path: ${{ steps.fixtures.outputs.pluginval }}
           args: --skip-gui-tests
@@ -119,7 +119,7 @@ jobs:
 
       - name: "Action: acceptance"
         id: acceptance
-        uses: ./.github/actions/acceptance
+        uses: ./acceptance
         with:
           pluginval-path: ${{ steps.fixtures.outputs.pluginval }}
           config-dir: build/action-fixtures/good
@@ -128,7 +128,7 @@ jobs:
       - name: "Action: acceptance (bad configs, expected to fail)"
         id: acceptance-bad
         continue-on-error: true
-        uses: ./.github/actions/acceptance
+        uses: ./acceptance
         with:
           pluginval-path: ${{ steps.fixtures.outputs.pluginval }}
           config-dir: build/action-fixtures/bad
@@ -137,15 +137,15 @@ jobs:
       - name: "Action: acceptance (missing reference, expected to fail)"
         id: acceptance-missing
         continue-on-error: true
-        uses: ./.github/actions/acceptance
+        uses: ./acceptance
         with:
           pluginval-path: ${{ steps.fixtures.outputs.pluginval }}
           config-dir: build/action-fixtures/missing
           plugin: build/tests/test_plugins/tone_generator/pluginval_tone_generator_artefacts/Release/VST3/pluginval Tone Generator.vst3
 
       - name: "Action: acceptance (record the missing reference)"
         id: acceptance-record
-        uses: ./.github/actions/acceptance
+        uses: ./acceptance
         with:
           pluginval-path: ${{ steps.fixtures.outputs.pluginval }}
           config-dir: build/action-fixtures/missing

CHANGELIST.md

@@ -6,7 +6,7 @@
 - Added `--junit-xml <file>` and `--json-results <file>` to both `pluginval validate` and `pluginval test` to write machine-readable reports for CI (also settable as `JUNIT_XML` / `JSON_RESULTS`). A report that can't be written fails the run. See `docs/Adding pluginval to CI.md`
 - Added acceptance testing: `pluginval test <config.json>` renders a plugin with a known state, input (audio/MIDI) and optional playhead, then compares the output against a checked-in reference WAV, exiting `0` on a match and `1` on a mismatch (with a diff WAV). Use `--record-missing` to record new references. See `docs/Acceptance testing.md`
 - Added `--plugin <plugin>` to `pluginval test` to run a config against a given plugin instead of the one it names (the config's `plugin` can then be omitted)
-- Added two GitHub Actions for use from other repositories: `Tracktion/pluginval/.github/actions/validate` (validate a list of plugins) and `.../acceptance` (run every acceptance config in a directory against a built plugin). See `.github/actions/README.md`
+- Added two GitHub Actions for use from other repositories: `Tracktion/pluginval/validate` (validate a list of plugins) and `Tracktion/pluginval/acceptance` (run every acceptance config in a directory against a built plugin). See `.github/actions/README.md`
 - Restructured the command line into subcommands: `pluginval validate [options] <plugin>` (the default), `pluginval run-tests` and `pluginval strictness-help [level]`. The plugin path is now a positional argument of `validate`
 - **Deprecated:** the flat flags `--validate <plugin>`, `--run-tests` and `--strictness-help [level]` still work as aliases (with a one-line notice) but will be removed in a future version. `pluginval <plugin>` remains a silent shorthand for `validate`
 - Replaced the hand-rolled command-line parser with CLI11 and a single JSON-based settings pipeline

CLAUDE.md

@@ -122,8 +122,10 @@ pluginval/
 │   ├── mac_tests/            # macOS-specific tests
 │   └── windows_tests.bat     # Windows test scripts
 ├── .github/
-│   ├── actions/              # Composite actions for other repos: validate/, acceptance/, common/ (see README.md there)
+│   ├── actions/              # Scripts + README for the composite actions: validate/, acceptance/, common/
 │   └── workflows/            # build.yaml (release build), acceptance.yml (acceptance self-tests + action dogfooding)
+├── validate/action.yml       # Composite action: Tracktion/pluginval/validate (runs .github/actions/validate/validate.sh)
+├── acceptance/action.yml     # Composite action: Tracktion/pluginval/acceptance (runs .github/actions/acceptance/acceptance.sh)
 ├── docs/                     # Documentation
 │   ├── Adding pluginval to CI.md
 │   ├── Command line options.md
@@ -530,16 +532,19 @@ add_pluginval_tests(MyPluginTarget
 
 ### GitHub Actions
 
-Two composite actions for other repositories live in `.github/actions/`
-(documented in `.github/actions/README.md`):
+Two composite actions for other repositories, referenced as
+`Tracktion/pluginval/validate@v2` and `Tracktion/pluginval/acceptance@v2`. Only
+their `action.yml` files sit at the repo root (`validate/`, `acceptance/`), to
+keep those references short; the scripts and `README.md` are in `.github/actions/`:
 
 - `validate/` - validates a newline-separated list of plugins / globs / AU ids.
 - `acceptance/` - runs `pluginval test` for every `*.json` (recursively, skipping
   the `*.wav.json` manifests and rejecting array configs) under a directory,
   optionally passing one built plugin via `--plugin`.
 
 Each `action.yml` only maps its inputs to `INPUT_*` environment variables and
-runs its sibling bash script (`validate.sh` / `acceptance.sh`); shared helpers
+runs its bash script (`.github/actions/validate/validate.sh` / `acceptance/acceptance.sh`,
+found relative to `$GITHUB_ACTION_PATH`); shared helpers
 (downloading the release or using `pluginval-path`, the Linux `xvfb-run` wrapper)
 are in `common/common.sh`. The scripts must stay bash 3.2 compatible (macOS
 runners) and can be run locally by setting the `INPUT_*` variables. They run
@@ -601,7 +606,7 @@ Run internal tests via CLI:
 4. Tag: `git tag -a vX.Y.Z -m "X.Y.Z release"`
 5. Push: `git push --tags`
 6. Once the release binaries are published, bump the `pluginval-version` default
-   in both `.github/actions/*/action.yml` (and the README tables) to the new tag
+   in `validate/action.yml` and `acceptance/action.yml` (and the README tables) to the new tag
 
 A tag with a hyphen (e.g. `v2.0.0-beta1`) is published as a pre-release, so it
 doesn't become the "latest" release that the download URLs in the docs point at.

.github/actions/acceptance/action.yml acceptance/action.yml.github/actions/acceptance/action.yml renamed to acceptance/action.yml

@@ -52,4 +52,5 @@ runs:
         INPUT_REPORT_DIR: ${{ inputs.report-dir }}
         INPUT_PLUGINVAL_VERSION: ${{ inputs.pluginval-version }}
         INPUT_PLUGINVAL_PATH: ${{ inputs.pluginval-path }}
-      run: bash "$GITHUB_ACTION_PATH/acceptance.sh"
+      # The scripts live in .github/actions so only this file sits at the repo root.
+      run: bash "$GITHUB_ACTION_PATH/../.github/actions/acceptance/acceptance.sh"

docs/Acceptance testing.md

@@ -104,7 +104,7 @@ On GitHub Actions, the `acceptance` action runs every config in a directory
 (recursively) against a built plugin:
 
 ```yaml
-- uses: Tracktion/pluginval/.github/actions/acceptance@v2
+- uses: Tracktion/pluginval/acceptance@v2
   with:
     config-dir: tests/acceptance
     plugin: build/MyPlugin_artefacts/Release/VST3/MyPlugin.vst3

docs/Adding pluginval to CI.md

@@ -13,7 +13,7 @@ There a couple of different ways this can be done but the simplest is as follows
 On GitHub Actions the simplest route is the `validate` action, which downloads pluginval, validates each plugin and fails the job if any fail:
 
 ```yaml
-- uses: Tracktion/pluginval/.github/actions/validate@v2
+- uses: Tracktion/pluginval/validate@v2
   with:
     plugins: |
       build/MyPlugin_artefacts/Release/VST3/MyPlugin.vst3

.github/actions/validate/action.yml validate/action.yml.github/actions/validate/action.yml renamed to validate/action.yml

@@ -49,4 +49,5 @@ runs:
         INPUT_REPORT_DIR: ${{ inputs.report-dir }}
         INPUT_PLUGINVAL_VERSION: ${{ inputs.pluginval-version }}
         INPUT_PLUGINVAL_PATH: ${{ inputs.pluginval-path }}
-      run: bash "$GITHUB_ACTION_PATH/validate.sh"
+      # The scripts live in .github/actions so only this file sits at the repo root.
+      run: bash "$GITHUB_ACTION_PATH/../.github/actions/validate/validate.sh"