-
Notifications
You must be signed in to change notification settings - Fork 35
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
chore: test CI #228
chore: test CI #228
Conversation
Since the only change was to update a test name, from the CI runs on the 6135edf commit we know something is wrong in the CI, probably after a external change in either github environment or one of out dependencies. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems strange to me we'd have to explicitly add this to the CI setup to have it work.
Assuming the issue comes from a dependency, could you try importing the changes from #226 in your branch instead, or maybe we can merge #226 if you can approve it and you can pull the main branch in #227, what do you think?
Yes, I'll try approving the release and then importing the changes to #227 , I also thought it was weird. |
PR to test CI
TODO