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 noticed in this draft PR that we are removing the "Default settings" fieldset entirely from Advanced Settings: #10367
If we do that, then users won't be able to tell what their previous configuration was. Since we still keep the database fields, we have two alternative options:
Disable these input fields so the values are still visible
Output their values in a table, given that the project still hasn't migrated to .readthedocs.yaml
The "use case" for this would be projects that haven't acted on the deprecation, presumably because they weren't building anything in the deprecation period and didn't find it necessary to migrate yet.
The text was updated successfully, but these errors were encountered:
We kept showing these values as read-only for a few months after the deprecation. Now, we have deleted them from the form and we are deleting them from the db as well in #11124. There is nothing else to do here now.
Refs: #10342
I noticed in this draft PR that we are removing the "Default settings" fieldset entirely from Advanced Settings: #10367
If we do that, then users won't be able to tell what their previous configuration was. Since we still keep the database fields, we have two alternative options:
.readthedocs.yaml
The "use case" for this would be projects that haven't acted on the deprecation, presumably because they weren't building anything in the deprecation period and didn't find it necessary to migrate yet.
The text was updated successfully, but these errors were encountered: