Skip to content

ci: fix success job #270

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
Jul 17, 2024
Merged

ci: fix success job #270

merged 1 commit into from
Jul 17, 2024

Conversation

CBenoit
Copy link
Member

@CBenoit CBenoit commented Jul 15, 2024

GitHub considers skipped job as green when it comes to merging pull requests. We need to make the success job fails for real if any previous job is failed.

@CBenoit CBenoit requested review from a team as code owners July 15, 2024 09:44
@CBenoit CBenoit enabled auto-merge (squash) July 15, 2024 09:45
@CBenoit CBenoit disabled auto-merge July 15, 2024 09:45
@CBenoit CBenoit force-pushed the ci-fix-success-job branch from e9ed2a1 to 043d592 Compare July 15, 2024 10:00
@CBenoit CBenoit enabled auto-merge (squash) July 16, 2024 03:26
@CBenoit CBenoit disabled auto-merge July 16, 2024 03:42
@CBenoit CBenoit enabled auto-merge (squash) July 16, 2024 03:43
It seems that GitHub considers skipped job as green when it comes to
merging pull requests. We need to make the success job fails for real
if any previous job is failed.
@CBenoit CBenoit force-pushed the ci-fix-success-job branch from 4d2b96f to 932bac3 Compare July 17, 2024 14:17
@CBenoit
Copy link
Member Author

CBenoit commented Jul 17, 2024

Rebased on master to get the windows build fix

@CBenoit CBenoit merged commit c1de0a9 into master Jul 17, 2024
42 checks passed
@CBenoit CBenoit deleted the ci-fix-success-job branch July 17, 2024 14:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants