You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found the ReadTheDocs configuration file documentation. The config file readthedocs.yml is currently in beta state.
Why did you name it so, especially without a leading dot?
All other cloud based services, configured by a *.yml file I know of, are using this format: .service.yml.
The text was updated successfully, but these errors were encountered:
There's no strong reason for it one way or the other, and certainly no standard for this. A number of services and local tooling use non-hidden files, so we followed suit. This is not just a configuration for our service, this file was meant to eventually allow for local execution as well -- to produce a similar command chain as our servers.
I could certainly see having an alternative naming for folks that would rather have these files hidden though. This would be implemented on https://github.com/rtfd/readthedocs-build. Closing the issue here, if anyone wants to take this on, the work should be fairly minimal to support a secondary .readthedocs.yml file.
I found the ReadTheDocs configuration file documentation. The config file
readthedocs.yml
is currently in beta state.Why did you name it so, especially without a leading dot?
All other cloud based services, configured by a
*.yml
file I know of, are using this format:.service.yml
.The text was updated successfully, but these errors were encountered: