Exclude tools requiring feature flag from docs#1721
Merged
SamMorrowDrums merged 7 commits intomainfrom Jan 5, 2026
Merged
Conversation
Collaborator
SamMorrowDrums
left a comment
There was a problem hiding this comment.
The outcome is correct, but I think we could use existing filters to do the filtering, by providing an always false feature flag checker.
Contributor
There was a problem hiding this comment.
Pull request overview
This PR modifies the documentation generation logic to exclude tools that require feature flags (marked with FeatureFlagEnable) from the generated README.md documentation, as these tools are not available to regular users. The change ensures that consolidated actions tools, which are behind a feature flag, don't appear in the public documentation.
Key Changes
- Modified documentation generation to use
AvailableTools()with feature flag filtering instead ofAllTools() - Explicitly set all toolsets to be enabled during documentation generation
- Tools requiring feature flags (
FeatureFlagEnable) are now excluded from the README
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| cmd/github-mcp-server/generate_docs.go | Updated inventory building to explicitly enable all toolsets and changed from AllTools() to AvailableTools() to respect feature flag filtering |
| README.md | Removed documentation for 4 consolidated actions tools (actions_get, actions_list, actions_run_trigger, get_job_logs) that require the FeatureFlagConsolidatedActions feature flag |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Mind-Vault-AI
approved these changes
Jan 2, 2026
Mind-Vault-AI
approved these changes
Jan 2, 2026
1 task
SamMorrowDrums
approved these changes
Jan 5, 2026
Collaborator
SamMorrowDrums
left a comment
There was a problem hiding this comment.
Nice one, beautiful!
Mind-Vault-AI
approved these changes
Jan 5, 2026
Mind-Vault-AI
approved these changes
Jan 5, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This pull request updates the way documentation is generated for available GitHub toolsets. The change is that the generated documentation now only includes tools that are normally available to users, rather than polluting the documentation by listing all possible tools. This results in not including those tools that are disabled or behind feature flags.
Why
What changed
Documentation and Tool Availability Updates:
README.md:actions_get,actions_list,actions_run_trigger, andget_job_logs, as these are no longer available to regular users. [1] [2]generate_docs.goto include only tools available to regular users by specifying the toolset filterWithToolsets([]string{"all"}).MCP impact
Prompts tested (tool changes only)
Security / limits
Tool renaming
deprecated_tool_aliases.goNote: if you're renaming tools, you must add the tool aliases. For more information on how to do so, please refer to the official docs.
Lint & tests
./script/lint./script/testDocs