-
Notifications
You must be signed in to change notification settings - Fork 148
🔒 Enable GitHub Lockdown Mode Security Feature by default in public repos #15289
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
This PR adds comprehensive documentation for the GitHub Lockdown Mode security feature, which filters public repository content to only show issues, PRs, and comments from users with push access. This protects agentic workflows from processing potentially malicious or misleading input from untrusted users in public repositories.
Changes:
- Created detailed reference documentation explaining lockdown mode security benefits, configuration, and use cases
- Integrated lockdown mode information into architecture documentation and security layers table
- Added FAQ entry and troubleshooting guidance for lockdown mode access issues
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 5 comments.
Show a summary per file
| File | Description |
|---|---|
| docs/src/content/docs/reference/lockdown-mode.md | New comprehensive reference page documenting lockdown mode features, security benefits, configuration options, safe use cases, and when to keep it enabled |
| docs/src/content/docs/reference/tools.md | Updated GitHub tools section with concise lockdown mode description and link to full documentation |
| docs/src/content/docs/reference/faq.md | Added FAQ entry explaining what lockdown mode is and when it's enabled |
| docs/src/content/docs/troubleshooting/common-issues.md | Added troubleshooting section for lockdown mode blocking expected content with symptoms, causes, and solutions |
| docs/src/content/docs/introduction/architecture.mdx | Added lockdown mode section to security architecture overview and added entry to security layers table |
Comments suppressed due to low confidence (1)
docs/src/content/docs/reference/lockdown-mode.md:201
- Incorrect field name in safe-outputs configuration. The field should be
allowed, notlabels. According to the safe-outputs documentation, add-labels usesallowedto restrict to specific labels. The correct syntax is:
safe-outputs:
add-labels:
allowed: ["spam", "needs-review"] add-labels:
labels: ["spam", "needs-review"]
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Summary
Key Changes
lockdown-mode.mdexplaining:architecture.mdxwith lockdown mode overview and security tableSecurity Considerations
Lockdown mode provides an additional layer of protection for public repositories by filtering content from untrusted sources, helping prevent potential security risks in automated workflows.