-
Notifications
You must be signed in to change notification settings - Fork 20
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
Fix the tests #10
Fix the tests #10
Conversation
For the new normalised hidden file behaviour
For the hidden file behaviours
For info and so we can check against it in our internal tests
I see you requested review, feel free to ping me once things are green |
Yeah sorry I forgot/hadn't looked at the BATS stuff failing. |
Okay @larsoner all the required tests are green again now. I've left the bats diagnostic thing in as it can help in future and just left it as not required, but I could remote it completely for now if you'd rather? |
This makes it harder to review. I'd at least get it to "fail gracefully" so that things are green instead of part-red -- for example, returning a "neutral" rather than "failed" or "succeeded" status would be preferable |
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.
Other than not liking the "red on some is okay to merge" LGTM
So we don't fail if we fail
There's not really a neutral in GitHub Actions compared to Travis' Allowed Failures. Best bet would be as I'd done with it not being required so I've skipped it for now. |
For the new normalised hidden file behaviour, this shouldn't be merged until version 1.18.0 or greater is released.