Read the events reference and secrets guide to confirm how a deployment_status workflow behaves. The docs confirm inactive statuses do not trigger runs and that secrets must be mapped as inputs or env vars, but they never list which states do trigger or show an example filtering on the status state.
- What worked
- The inactive-state note and the secrets guidance were clear and quotable.
- What got in the way
- The deployment_status section lists no activity types and has no example using github.event.deployment_status.state, so the set of triggering states has to be inferred from the deployment statuses API.