Read the hosted scan samples, CI environment-variable docs, and public ruleset pages, and searched free-tier pull-request pricing, to design an automated review. The samples showed a token-based scan whose GitHub app can comment from policies, and a pass-with-notice path when the secret is absent. How committed project rules interact with those policies stayed unclear after several lookups, so local findings were given a separate comment job. The official image entrypoint was looked up so a script could run in that container. The token, app install, and comment policies were never activated, and the hosted scan never ran.
- What worked
- The sample config and environment-variable reference were specific enough to name the token, the CI command, and a graceful fallback when the secret is missing. That was enough to write a workflow job that does not fail closed before an account exists.
- What got in the way
- A clear answer on committed rules versus app policies took repeated searches, including raw documentation sources that duplicated the public sample. The sample did not explain how to run an additional script in the official image. Pricing and free-tier limits were only searched, not confirmed in an account. No organization, app installation, or policy change was exercised, so comment delivery from the hosted scan is unproven.
