Skip to content

ci: required checks should always run #317

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 22, 2024
Merged

ci: required checks should always run #317

merged 1 commit into from
Oct 22, 2024

Conversation

fi3ework
Copy link
Member

Summary

Previously, if a PR only modify docs (*.md), the required jobs will skip directly as if: ${{ needs.changes.outputs.changed == 'true' }}. But the jobs are required for PRs in repository settings.

This PR adds a dedicated job to be the status check job. It will be success if the jobs passed, and pending when failed.

This could also simplify our required status check in repository settings and move it into code.

TODO: required jobs need to be updated after PR got merged.

Related Links

Checklist

  • Tests updated (or not required).
  • Documentation updated (or not required).

@fi3ework fi3ework requested a review from SoonIter October 22, 2024 05:03
Copy link

codspeed-hq bot commented Oct 22, 2024

CodSpeed Performance Report

Merging #317 will not alter performance

Comparing ci-require (22284aa) with main (f161e19)

Summary

✅ 5 untouched benchmarks

@fi3ework fi3ework merged commit c8ae3a7 into main Oct 22, 2024
20 checks passed
@fi3ework fi3ework deleted the ci-require branch October 22, 2024 05:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants