Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This draft PR is just for feedback on the proposed structure, it won't be merged. The final PR will also need to update xrefs.
It enables local builds for testing, using the same theme as the SDK.
It (and most repos) would look like this in the SDK docs:
For simpler repos (dwave-inspector here), we can always have at least one page:
Or (penaltymodel here) we can either directly go to the API:
I like always having at least one underlying page for consistency and aesthetics but some people prefer one fewer click.
I can make draft PRs for the penaltymodel branch and dwave-inspector branch if that is helpful.
For now I'm taking advantage of GitHub's perfectly decent rendition of release notes but later if we want to spend the time working around reno's duplication of anchors between repos to prevent dozens of warnings, we can generate HTML for those again.