Docker pre.entrypoint links to Node pre.pre-if

[jsoref]

Code of Conduct

• I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/actions/sharing-automations/creating-actions/metadata-syntax-for-github-actions#runspre-entrypoint

What part(s) of the article would you like to see updated?

I think a distinct .pre-if should be added to the https://docs.github.com/en/actions/sharing-automations/creating-actions/metadata-syntax-for-github-actions#runs-for-docker-container-actions and https://docs.github.com/en/actions/sharing-automations/creating-actions/metadata-syntax-for-github-actions#runspre-entrypoint's runs.pre-if link should be changed to point to it.

Additional information

Here's a run with pre-if: true:

  pre-entrypoint: '/pre.sh'
  pre-if: true

pre

Here's a run with pre-if: false (which is good because the pre-entrypoint was broken):

  pre-entrypoint: 'pre.sh'
  pre-if: false

https://github.com/check-spelling-sandbox/bookish-rotary-phone/actions/runs/11798769996/job/32865715637

[jsoref]

I'm not sure how easy it would be to split the two pre-if statements two get distinct anchors. Offhand, I'd strongly recommend splitting the document into:

1. page for actions in general that links to individual pages for javascript, composite, and docker
2. reusable shared-action-definitions head basically everything from https://docs.github.com/en/actions/sharing-automations/creating-actions/metadata-syntax-for-github-actions#about-yaml-syntax-for-github-actions stopping before runs
3. page for JavaScript actions with includes for reusable shared-action-definitions head and reusable shared-action-definitions tail
4. page for composite actions with includes for reusable shared-action-definitions head and reusable shared-action-definitions tail
5. page for Docker container actions with includes for reusable shared-action-definitions head and reusable shared-action-definitions tail
6. reusable shared-action-definitions tail with branding

The number of people who want to look at the syntax for more than one kind of action at a time can be counted on one hand and they all more or less work on either actions/runner or nektos/act. Everyone else only cares about one kind of action (on average javascript or composite) and doesn't need to be confused by the other two.

[nguyenalex836]

@jsoref Thank you for raising this issue! I'll get this triaged for review ✨ Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛

[github-actions]

Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert 👀