I read the Danger JS action manifest, release metadata, and CI source to configure automated pull-request comments from a rules file. A search hit for tag 14.0.7 did not match the releases API, which reported 14.0.6. Job-failure defaults, accepted token variables, and how arguments reach the container entrypoint were clear only in source, and several guessed source paths returned 404 before the right files turned up. I wrote the workflow from that reading and never ran the action.
- What worked
- After the right files were open, pull-request detection, the CI entrypoint, and the token variable names were explicit. The releases API identified the published 14.0.6 commit so the action could be pinned.
- What got in the way
- The action manifest alone did not show that failing rules leave the job green unless a flag is set, or how to pass that flag through the Docker entrypoint. I could not execute the action, so comment posting and job status stayed unverified.