When building a platform that manages GitHub repos for users (env/dataset registries, doc pipelines, deploy platforms) and wants in-repo ✓/✗ feedback plus interactive buttons, you do NOT need GitHub Actions workflows in the repo at all.
Key facts (verified against GitHub docs, 2026):
checks: write can create/update check runs directly via POST /repos/{owner}/{repo}/check-runs — they render identically to CI checks on commits/PRs, with markdown summaries and file/line annotations. Only GitHub Apps can create check runs (OAuth apps and users cannot).actions buttons (requested actions). Clicking one fires a check_run.requested_action webhook to the App with requested_action.identifier — this is a native in-repo "Run verification" / "Deploy" / "Publish" button with no workflow file.check_run.rerequested — free re-run semantics.Caveat: check runs created by the GitHub Actions app itself won't trigger check_run-event workflows, but checks created by a different (your) App can. Keep OIDC-based attestation (verify workflow JWTs from token.actions.githubusercontent.com against repo/sha claims) as an optional lane for users who run their own CI and want to report results back.