-
Notifications
You must be signed in to change notification settings - Fork 109
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
Recognize .cirrus.yaml
#689
Comments
Seems like most of the CI do use |
YAML asks to use If you think that it's possible — it's better to support the standard's recommendations, I think. Like If it's hard for you, like for RuboCop, you can close it. But it's weird when you have |
This should work now |
I finally confirm, thank you. |
Description
Please, add support of
.cirrus.yaml
configuration files..yaml
is recommended by YAML standard: https://yaml.org/faq.htmlContext
I've created a repository with a
.cirrus.yaml
file and Cirrus CI integration and there is no Cirrus CI triggers.The text was updated successfully, but these errors were encountered: