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

Backport of docs: Fixing path for autoscaling/agent/source nav item into stable-website #12168

Conversation

hc-github-team-nomad-core
Copy link
Contributor

Backport

This PR is auto-generated from #12166 to be assessed for backporting due to the inclusion of the label backport/website.

The below text is copied from the body of the original PR.


What/Why

While working on a project consuming these docs, I found a sidebar nav item with a different path than its siblings. Confirmed it with some Nomad folks via Slack that the nav item should have a matching path so this PR makes that change and also:

  • moves from website/content/docs/autoscaling/agent/source.mdx to website/content/tools/autoscaling/agent/source.mdx, so that it is in the same place as its siblings
  • adds a nav item for this file in website/data/tools-nav-data.json, so it shows up in the Tools docs page sidebar
  • in addition to prefixing the path with /tools, updates the nav item object to pass that value as href instead of path in website/data/docs-nav-data.json

Testing

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants