github
"Actions Runner Controller" articles expand wrong tree item
Code of Conduct
- [X] I have read and agree to the GitHub Docs project's Code of Conduct
What article on docs.github.com is affected?
Self-hosted runners > Actions Runner Controller:
- About Actions Runner Controller
- Quickstart for Actions Runner Controller
- Authenticating to the GitHub API
- Deploying runner scale sets with Actions Runner Controller
- Using Actions Runner Controller runners in a workflow
- Troubleshooting Actions Runner Controller errors
- About support for Actions Runner Controller
What part(s) of the article would you like to see updated?
All the pages above, expand the following tree item:
Self-hosted runners > Manage self-hosted-runners
[Actual]
[Expected]
Additional information
I've already looked at docs/content/README.md, but couldn't figure out how the tree state is set. Happy to raise a PR myself if you point me in the right direction 🙏
@hsnabszhdn Thank you for raising this issue! I'll get this triaged for review :sparkles: Our team will provide feedback regarding the best next steps for this issue - thanks for your patience! 💛
Thanks for opening an issue! We've triaged this issue for technical review by a subject matter expert :eyes:
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Thanks for raising that @hsnabszhdn, I agree it's odd—we'll look into this and update you when we figure out what's happening.
This is a gentle bump for the docs team that this issue is waiting for technical review.
This is a gentle bump for the docs team that this issue is waiting for technical review.
This is a gentle bump for the docs team that this issue is waiting for technical review.
This is a gentle bump for the docs team that this issue is waiting for technical review.
This is a gentle bump for the docs team that this issue is waiting for technical review.
@hsnabszhdn - many thanks for your patience while we've worked out what's going on here.
We have determined that this will need to be fixed internally by another team. Since we're tracking the work internally now, I'm going to close this issue.
