Skip to content
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

[core] Fix failing CI on HEAD #23947

Merged
merged 1 commit into from
Dec 10, 2020
Merged

Conversation

oliviertassinari
Copy link
Member

Capture d’écran 2020-12-10 à 20 39 02

@mui-pr-bot
Copy link

mui-pr-bot commented Dec 10, 2020

No bundle size changes

Generated by 🚫 dangerJS against d63a3d3

Copy link
Member

@mnajdova mnajdova left a comment

Choose a reason for hiding this comment

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

Oops, thanks for fixing it. How did I missed this? Why wasn’t it failing on the PR?

@oliviertassinari oliviertassinari merged commit 83218b3 into mui:next Dec 10, 2020
@oliviertassinari oliviertassinari deleted the head-fix branch December 10, 2020 21:27
@oliviertassinari
Copy link
Member Author

Not sure, maybe #23745 wasn't rebased on HEAD.

@eps1lon
Copy link
Member

eps1lon commented Dec 10, 2020

Oops, thanks for fixing it. How did I missed this? Why wasn’t it failing on the PR?

Our CI only runs on the original branch and never on the potential merge commit. So if it's behind it's target branch the CI run isn't fully reliable. We occasionally have these integration issues but it's so rare that it isn't really worth it to run CI twice as often.

No worries though. As long as CI is failing before we publish nothing happens. It would only be problematic if we deploy before CI passes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants