Add instructions how to use status check outside if conditionals

[arxeiss]

Why:

Closes: #39463

We want to send Slack message when job succeed, but also fails. And we had 2 action steps with same setup, except the message. By coincidence I have found that you can use job.status too. But it is not mentioned in the Status check functions. So I simply thought it is not possible at all.

After my finding, I was able to convert this

- name: Slack Notification Success
  if: success()
  uses: slackapi/slack-github-action@91efab103c0de0a537f72a35f6b8cda0ee76bf0a # v2.1.1 - https://github.com/slackapi/slack-github-action/releases
  with:
      token: ${{ secrets.SLACK_BOT_TOKEN }}
      method: chat.postMessage
      payload: |
          {
            "channel": "${{ secrets.SLACK_CHANNEL_FOR_DEPLOYMENT }}",
            "text": "✅ *${{ inputs.env-values-path }}:* deployed successfully",
            "thread_ts": "${{ inputs.slack_thread }}"
          }
- name: Slack Notification Failure
  if: failure()
  uses: slackapi/slack-github-action@91efab103c0de0a537f72a35f6b8cda0ee76bf0a # v2.1.1 - https://github.com/slackapi/slack-github-action/releases
  with:
      token: ${{ secrets.SLACK_BOT_TOKEN }}
      method: chat.postMessage
      payload: |
          {
            "channel": "${{ secrets.SLACK_CHANNEL_FOR_DEPLOYMENT }}",
            "text": "❌ *${{ inputs.env-values-path }}:* deployment failed. Check the pipeline ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}",
            "thread_ts": "${{ inputs.slack_thread }}"
          }

into

- name: Slack Notification Success
  if: success() || failure()
  uses: slackapi/slack-github-action@91efab103c0de0a537f72a35f6b8cda0ee76bf0a # v2.1.1 - https://github.com/slackapi/slack-github-action/releases
  with:
      token: ${{ secrets.SLACK_BOT_TOKEN }}
      method: chat.postMessage
      payload: |
          {
            "channel": "${{ secrets.SLACK_CHANNEL_FOR_DEPLOYMENT }}",
            "thread_ts": "${{ inputs.slack_thread }}",
            "text": "${{ job.status == 'success'
                && format(':white_check_mark: *{0}:* deployed successfully', inputs.env-values-path)
                || format(':x: *{0}:* deployment failed. Check the pipeline {1}/{2}/actions/runs/{3}', inputs.env-values-path, github.server_url, github.repository, github.run_id)
            }}"
          }

What's being changed (if available, include any code snippets, screenshots, or gifs):

Adding 1 more paragraph to Status check functions with link to https://docs.github.com/en/actions/reference/contexts-reference#job-context describing how to access same info like success() / failure() outside if conditionals

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
actions/reference/workflows-and-actions/expressions.md	fpt ghec ghes@ 3.17 3.16 3.15 3.14	fpt ghec ghes@ 3.17 3.16 3.15 3.14

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Sharra-writes]

@arxeiss Thanks for opening an issue and PR about this! I'm glad you found a function that made your life easier. I'll definitely look into why it's not documented and whether it should be!

[arxeiss]

@Sharra-writes any updates on this? In my opinion this is still valid update.

If my PR is missing anything, let me know

[Sharra-writes]

@arxeiss The only update is that I have a really long queue of questions about Actions, and the team is responding slowly in part because people have been/are on vacation, and in part because Actions is complicated with a lot of specialization. This hasn't fallen off my list.

[arxeiss]

Understand. Thank you for update

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡