You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[plan] Add fork context warning to validate_secrets.cjs #18519
actions/setup/js/validate_secrets.cjs validates that required secrets are present. In a forked repository, all secrets from the parent repo are absent. Currently the script reports each missing secret with a generic "not found" error, giving no hint that the fork context is the root cause.
Objective
Update validate_secrets.cjs to detect when running inside a fork (context.payload.repository.fork === true) and prepend a fork-context warning to the output, making it clear that all secrets must be independently configured in the fork.
Approach
In actions/setup/js/validate_secrets.cjs, read context.payload.repository.fork (the @actions/github context is already available).
If fork === true, emit a core.warning(...) at the top of the output like:
⚠️ This repository is a fork. Secrets from the parent repository are not inherited. You must configure each secret listed below directly in your fork's repository settings.
Keep the existing per-secret validation logic unchanged — just prefix the report.
Run make fmt-cjs && make lint-cjs to validate.
Add/update tests in validate_secrets.test.cjs covering the fork branch.
Activity