secret-scanning

Topics in the source

• Secret Scanning
• When to Use This Skill
• How Secret Scanning Works
• Availability
• Core Workflow — Enable Secret Scanning
• Step 1: Enable Secret Protection
• Step 2: Enable Push Protection
• Step 3: Configure Exclusions (Optional)

This skill provides procedural guidance for configuring GitHub secret scanning — detecting leaked credentials, preventing secret pushes, defining custom patterns, and managing alerts. Use this skill when the request involves: Enabling or configuring secret scanning for a repository or organization Setting up push protection to block secrets before they reach the repository Defining custom secret patterns with regular expressions Resolving a blocked push from the command line Triaging, dismissing, or remediating secret scanning alerts Configuring delegated bypass for push protection Excluding directories from secret scanning via secretscanning.yml Understanding alert types (user, partner, push protection) Enabling validity checks or extended metadata checks Scanning local code changes for secrets before committing (via MCP / AI coding agent) — see the Pre-Commit Scanning via AI Coding Agents section below for the recommended plugin Secret scanning automatically detects exposed credentials across: Entire Git history on all branches Issue descriptions, comments, and titles (open and closed) Pull request titles, descriptions, and comments GitHub Discussions titles, descriptions, and co

This is an excerpt. Refer to the complete source and its current requirements.