ci: add CI workflow to run plugin against itself#267
Merged
Conversation
## What Added a CI workflow and supporting script that builds the plugin, downloads the latest privateer release, and runs the plugin against the ossf/pvtr-github-repo-scanner repository to validate OSPS baseline Level 1 controls. ## Why The project had no integration-level CI to verify the plugin works end-to-end against a real GitHub repository. This mirrors the CI pattern used by the privateer project itself, giving confidence that changes don't break the plugin's evaluation capabilities. ## Notes - The workflow uses `secrets.GITHUB_TOKEN` with only `contents: read` — if OSPS controls query endpoints beyond basic repo content (branch protection, security advisories, Dependabot), additional permissions or a PAT may be needed. - The ci.sh script downloads the latest privateer release at runtime; a breaking change in privateer could cause CI failures unrelated to this repo's code. - The `tmp/` directory was added to .gitignore to support local runs of ci.sh. Signed-off-by: jmeridth <jmeridth@gmail.com>
eddie-knight
approved these changes
Mar 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TLDR I need this to feel comfortable when we merge PRs
What
Added a CI workflow and supporting script that builds the plugin, downloads the latest privateer release, and runs the plugin against the ossf/pvtr-github-repo-scanner repository to validate OSPS baseline Level 1 controls.
Why
The project had no integration-level CI to verify the plugin works end-to-end against a real GitHub repository. This mirrors the CI pattern used by the privateer project itself, giving confidence that changes don't break the plugin's evaluation capabilities.
Notes
secrets.GITHUB_TOKENwith onlycontents: read— if OSPS controls query endpoints beyond basic repo content (branch protection, security advisories, Dependabot), additional permissions or a PAT may be needed.tmp/directory was added to .gitignore to support local runs of ci.sh.