Enable lockdown mode and public repository filtering for stale-repo-identifier workflow #5376
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.
The stale-repo-identifier workflow needs to operate in lockdown mode and only analyze public repositories to prevent exposure of untrusted content.
Changes
GitHub MCP Configuration
lockdown: trueto limit content from public repos to items authored by users with push accessread-only: trueto enforce read-only operationsWorkflow Instructions
Trending and Cache Memory
cache-memorytool for persistent data storage across workflow runsshared/trending-charts-simple.mdfor trending visualization capabilitiesConfiguration
The lock file uses local Docker-based GitHub MCP server with
GITHUB_LOCKDOWN_MODE=1andGITHUB_READ_ONLY=1environment variables.Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.