Context Navigation

Changes between Initial Version and Version 1 of Ticket #50401, comment 41

initial	v1
8	8	- Enable an individual workflow to function for pull requests on the fork as they would for the mirror. (`WP_*_PR`)
9	9
10		These secrets can be defined at the repository or organization~~/user level~~.
	10	These secrets can be defined at the repository or organization level, making it easy to define for just one repo, or throughout the organization (if, for some reason, multiple forks/mirrors of `wordpress-develop` are maintained).
11	11
12	12	It seems `secrets` and `env` variables are not available to the job specific `if:`s within the workflow file. `secrets` can be used in steps, but [https://docs.github.com/en/free-pro-team@latest/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepswith only when provided as an input]. While `env` context is documented as available to `with` and `name` keys for a job, and `if` [https://docs.github.com/en/free-pro-team@latest/actions/reference/context-and-expression-syntax-for-github-actions#env-context conditionals for a step], environment variables defined at the [https://github.community/t/how-to-set-and-access-a-workflow-variable/17335/6 workflow level are not available at the job level].