-
-
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
Docs: Split up Pull Request Builds into a how-to guide and reference (Diátaxis) #9679
Docs: Split up Pull Request Builds into a how-to guide and reference (Diátaxis) #9679
Conversation
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.
"Requesting changes" here until we decide the next steps in the conversation we are having in #9676
Note for the future: we are renaming a file, so that we will require a redirect in place.
No files are renamed here, the old file stays in place and a new file is added. We have in the overall plan for this project to not remove any files, so we don't have to become distracted with file names, folder names nor redirects. |
203044f
to
345d9f5
Compare
bfeaa49
to
797a7f4
Compare
This is ready and reviewed. Site-note: Picked up a conversation about finding a repeatable pattern for "Only available on Sphinx" messages. But that can be introduced in another changeset. Merging this one... |
Refs #9746
📚 Documentation previews 📚
docs
): https://docs--9679.org.readthedocs.build/en/9679/dev
): https://dev--9679.org.readthedocs.build/en/9679/