-
Notifications
You must be signed in to change notification settings - Fork 32
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
Fixing CI from #711 #729
Fixing CI from #711 #729
Conversation
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Oh sorry, I shouldn't have done that @penelopeysm ; thought i was looking at another PR 🤦 |
haha don't worry 😄 |
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Think I fixed the issues now @penelopeysm :) |
Thanks for picking it up! |
Ohhhhh, I think I know what happened with the merge queue. I had to temporarily remove the required CI checks, because of #724 (otherwise it would wait forever on the macos x64 job that wasn't being run any more), and they haven't been added back yet, so it just merges right away without checking anything. I'll fix that in the repo settings and then I think we should be back to normal. |
#711
To be clear I introduced some of these errors when performing a manual merge, it's just that GitHub decided to merge the PR before I could see the outcome of CI