Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/build.yml
Original file line number Diff line number Diff line change
Expand Up @@ -153,7 +153,7 @@ jobs:
GPG_PASSWORD: ${{ secrets.GPG_PASSWORD }}

required-status-check:
if: github.event_name == 'pull_request'
if: github.event_name == 'pull_request' && always()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not following how this helps. Isn't && always() basically && true which is always true?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one would think...

check out https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/evaluate-expressions-in-workflows-and-actions#always

and you can see the difference below, required-status-check is run and fails (and so should block merging even after someone approves this PR), whereas in #1542 for example, required-status-check is skipped (and therefore didn't block merging)

needs:
- build
- integration-test
Expand Down
Loading