-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Stop creating a conf.py automatically and doing magic around README handling #5609
Conversation
…around README handling
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.
We need to remove the autocreated mkdocs.yaml for mkdocs projects too https://github.com/rtfd/readthedocs.org/blob/43c1ba7e8b65bc3bb5a8b2d7b7f6de94dfa91b44/readthedocs/doc_builder/backends/mkdocs.py#L88-L91
The index page generation should stay, this is another issue we need to resolve in another PR (right now we should generate an index if we don't find one)
@stsewd Updated the PR according to your suggestions. |
@stsewd Updated the PR |
resolved conflicts |
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.
Just a few details, this should be ready for merge after that.
….org into readme-creation-fix
@stsewd Updated the PR :) |
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.
Thanks!
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.
Thanks! Changes look good to me.
I'm a little worried about current projects that are building properly,
- without a
conf.py
file - with a
README
file instead of aindex.rst
What is our plan for those projects?
I'm marking as "Request changes" because of this reason to discuss what we want to do with those projects before merging it.
@@ -76,3 +76,7 @@ class MkDocsYAMLParseError(BuildEnvironmentError): | |||
'The "{config}" config from your MkDocs YAML config file has to be a ' | |||
'a list of relative paths.', | |||
) | |||
NOT_FOUND = ugettext_noop( | |||
'A configuration file was not found. ' | |||
'Make sure you have a "mkdocs.yaml" file in your repository.', |
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.
Not sure if it matters, but official MkDocs uses mkdocs.yml
to refer this file. I suppose it's better to follow their convention here.
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.
@humitos Fixed. :)
@humitos It was decided that if those project don't build locally, they shouldn't build in rtd neither. See #2483 (comment) |
@stsewd I think that is valid for new projects, but I don't think we want to break all the ones that are already building properly. Also, that seems like a comment from David to me, not a decision made. Do we know how many projects that matches the conditions that I mentioned are currently building? I suppose that at least we should contact them and make a deprecation plan giving them some time to migrate. |
We decided that,
Once we have collected this data and we gave some time to them to migrate, we can merge this PR. I'm marking as blocked until then. |
Before removing this, we want to collect some info to communicate this change to users. Related readthedocs#5609
We are ready to move forward with the plan I wrote in my previous comment #5609 (comment) So, the first step here is to add log lines to know what are the projects where we are creating a
It seems we are ready to start contacting these users about the removal of this feature. |
…adme-creation-fix
@humitos This needs to be merged after Aug 28 right? |
@humitos Great, I've added it to the sprint for that timeframe 👍 |
…adme-creation-fix
I need some input about the README handling. if that's what we want or not?