-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Build: run cat readthedocs.yaml
even when there is a config error
#11097
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
Comments
This issue would have been being helpful on this case #11173 where the user had two YAML file in the repository and Read the Docs was picking the incorrect one. |
I took a look at this and it seems we need to split the
Moving out 1) will allow us to know what's the file we will be loading and show it to the user before loading and validating. |
This moves the `cat readthedocs.yaml` command _before_ validating the YAML file. This allows the user to inspect the configuration file in case it fails due to a validation error. Closes #11097
I think this an okay first step to take, but discussed next steps on this particular command more in #7005. |
* Build: show the YAML config file before validating it This moves the `cat readthedocs.yaml` command _before_ validating the YAML file. This allows the user to inspect the configuration file in case it fails due to a validation error. Closes #11097 * Use a better name for the variable * Omit check for `cat readthedocs.yaml` for now We can't perform this check on the "build environment" because it happens in the "VCS environment" now and we are not mocking it. We should find a way to check these commands on the "VCS environment".
I just realized that we first validate the
readthedocs.yaml
file and then runcat readthedocs.yaml
to show its content. What happens? If there is a syntax error or a missing required value or anything, we don't run thecat
command. This makes hard to debug and understand what's going on.We should first run the
cat
command and after that validate the file. This will help a lot with UX.Example: https://beta.readthedocs.org/projects/test-builds/builds/23364407/
The text was updated successfully, but these errors were encountered: