We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Read the Docs wasn't building our documentation for some reason. It has started working now, but I noticed that it's now using the 1.1 branch as the "stable" release. See https://docs.citationstyles.org/en/stable/specification.html.
We could either rename the 1.1 branch to mark it as pre-release (see https://docs.readthedocs.io/en/stable/versions.html#versioned-documentation), or I can redirect https://docs.citationstyles.org/ to "1.0.1" instead of "stable" (although we probably link to "stable" in a bunch of places, so the former would be better).
cc @adam3smith, @bdarcus, @bwiernik
The text was updated successfully, but these errors were encountered:
Sorry, something went wrong.
Per readthedocs/readthedocs.org#3528, the cleanest option might be to add a "1.0.1" tag to the tip of the "1.0.1" branch.
Closing. Fixed by tagging the 1.0.1 branch with a "v1.0.1" (release) tag: https://github.com/citation-style-language/documentation/releases/tag/v1.0.1
No branches or pull requests
Read the Docs wasn't building our documentation for some reason. It has started working now, but I noticed that it's now using the 1.1 branch as the "stable" release. See https://docs.citationstyles.org/en/stable/specification.html.
We could either rename the 1.1 branch to mark it as pre-release (see https://docs.readthedocs.io/en/stable/versions.html#versioned-documentation), or I can redirect https://docs.citationstyles.org/ to "1.0.1" instead of "stable" (although we probably link to "stable" in a bunch of places, so the former would be better).
cc @adam3smith, @bdarcus, @bwiernik
The text was updated successfully, but these errors were encountered: