This repository was archived by the owner on Nov 24, 2025. It is now read-only.
Fix ordering in overview docs section#3906
Merged
Merged
Conversation
Put introduction first
Contributor
|
Refer to this link for build results (access rights to CI server needed): |
ocket8888
suggested changes
Sep 6, 2019
ocket8888
approved these changes
Sep 6, 2019
Contributor
ocket8888
left a comment
ocket8888
left a comment
There was a problem hiding this comment.
The maxdepth thing didn't work - not sure why - but other than that this compiles without warnings and has the desired effect.
Contributor
|
Refer to this link for build results (access rights to CI server needed): |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
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.
What does this PR (Pull Request) do?
Fix ordering in overview docs section
Introduction was not first which makes it confusing to the end user as they come in
Which Traffic Control components are affected by this PR?
What is the best way to verify this PR?
Build docs locally and look at ordering of overview section
If this is a bug fix, what versions of Traffic Control are affected?
The following criteria are ALL met by this PR