Skip to content
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

Suggests a v2 config file from the current options to help transition from v1 or web #4746

Closed
stsewd opened this issue Oct 10, 2018 · 5 comments
Labels
Feature New feature Needed: design decision A core team decision is required
Milestone

Comments

@stsewd
Copy link
Member

stsewd commented Oct 10, 2018

We don't have many settings on the conf file, but it will be a cool feature to have, and also it will help to migrate to v2.

It may depend on #4638

Ref #4732 (comment)

@stsewd stsewd added Feature New feature Needed: design decision A core team decision is required labels Oct 10, 2018
@humitos humitos added this to the Admin UX milestone Nov 14, 2018
@stsewd
Copy link
Member Author

stsewd commented Feb 22, 2019

We could warn in each build to a link with the new config or docs as suggested in #5338 (review)

@humitos
Copy link
Member

humitos commented May 25, 2019

In #5519 we added a message to communicate with users about the usage of a .readthedocs.yml config in the build output.

I think a cool idea would be to add a link to create this file with the specific content on their own repository. I found that adding ?filename=.readthedocs.yml to the link that creates the file into the GitHub repository we can name it properly. Although, I didn't find how to populate the content of it.

Example: https://github.com/rtfd/readthedocs.org/new/master?filename=.readthedocs.yml

Reference: https://github.blog/2012-12-05-creating-files-on-github/

@humitos
Copy link
Member

humitos commented May 25, 2019

That's exactly what I was looking for!

I think this is a really good usage for this,

  • we can generate the proper content depending on the user's settings
  • we are not being rude like by just performing a commit
  • we let the user to customize our content suggestion
  • immediately after the user makes the commit, we will trigger a new build with these new settings

I would add this link next to the message that promotes the usage of this file with so the user can create it by themselves, @davidfischer what do you think?

We can use "this technique" to suggest

  1. the content of the file to migrate from v1 to v2
  2. content of a new setting file for v2

@humitos
Copy link
Member

humitos commented Sep 15, 2023

We already deprecated v1 of the config file and we will remove it on October. I'm closing this issue because it's not valid anymore.

@humitos humitos closed this as completed Sep 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature Needed: design decision A core team decision is required
Projects
None yet
Development

No branches or pull requests

3 participants