Add needs: syntax example using always() condition

[remyleone]

Why:

It was confusing for me to understand how the different dependencies between jobs are working. Adding an example about conditional execution of jobs would have helped me understand more quickly how to solve a problem I had using GitHub action.

What's being changed:

I've added an example about how to mix conditional and dependencies between jobs to ensure that a job always gets executed regardless of the results of jobs it depends on.
This is particularly useful when you have a "cleanup/sweeper" kind of job that you want to execute regardless or whether or not previous jobs worked.

Check off the following:

• All of the tests are passing.
• I have reviewed my changes in staging.
• For content changes, I have reviewed the localization checklist
• For content changes, I have reviewed the Content style guide for GitHub Docs.

[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.

[SMAKSS]

Hi there, thanks for the PR, I guess, if you seeking any change or question about anything in the docs, you can use discussion or create a new issue instead to communicate about it.

[remyleone]

I can update the PR if I get confirmation that using

jobs:
  job1:
  job2:
    needs: job1
  job3:
    if: always()
    needs: [job1, job2]

is the canonical way to run job3 after job1 and job2 and whether or not job1 and job2 are successful or not

[janiceilene]

Thanks for opening a PR 👍 Please fill out the pull request template in the top comment in this pull request, then we'll get this up for review!

[remyleone]

@janiceilene done :)

[janiceilene]

Thanks so much @remyleone! I'll get this triaged for review 🌟

[github-actions]

This PR is stale because it has been open 7 days with no activity and will be automatically closed in 3 days. To keep this PR open, update the PR by adding a comment or pushing a commit.

[janiceilene]

@remyleone Thanks for your patience! Our small team is working our way through reviewing all of the amazing contributions ✨

[shati-patel]

(Just for information: I updated this PR from main to fix a merge conflict that came from #1389. I'll let someone from the Ecosystem docs team take a look at the actual changes, since they're more familiar with these topics!)

[github-actions]

This PR is stale because it has been open 7 days with no activity and will be automatically closed in 3 days. To keep this PR open, update the PR by adding a comment or pushing a commit.

[lucascosti]

Hi @remyleone, thanks a lot for this suggestion! 🙇‍♂️ Another example for this would definitely be helpful!

I've made some edits to your PR to fix failing tests as well as make it more consistent with our style and other examples.

Because I've made some significant changes myself, I'll get another writer on the team to review this before we merge it.

[martin389]

Thanks @lucascosti! Added some non-blocking personal preference suggestions.

[martin389]

I'll raise a docs issue for all the titles in this guide, so that we can move them to an "Example: verb" convention

[martin389]

Done: #2063 👍

[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.