By default,secret scanning is enabled automatically for all public repositories. For private or internal repositories, secret scanning must be enabled manually unless configured at the organization or enterprise level.
This default behavior helps protect open-source projects without requiring additional configuration.

By default,users with Write, Maintain, or Admin permissionswill receive notifications for new Dependabot alerts. However,Write permissionis theminimum levelneeded to be automatically notified.
Users with only Read access do not receive alerts unless added explicitly.

These three features provide a complete layer of defense:
* Code scanningidentifies security flaws in your source code
* Secret scanningdetects exposed credentials
* Dependency reviewshows the impact of package changes during a pull request Together, they give developers actionable insight into risk and coverage throughout the SDLC.

Toexclude.txt and .md files from triggering workflows on pull requests to the main branch:
* on: defines the event (e.g., pull_request)
* pull_request: is the trigger
* paths-ignore: is the key used to ignore file patterns
Example YAML:
yaml
CopyEdit
on:
pull_request:
branches:
- main
paths-ignore:
- '*.md'
- '*.txt'
Using paths: would include only specific files instead - not exclude. paths-ignore: is correct here.

All results from CodeQL analysis appear under therepository's code scanning alertstab. This section is part of theSecuritytab and provides a list of all current, fixed, and dismissed alerts found by CodeQL.
A CodeQL database is used internally during scanning but does not display results. Query packs contain rules, not results. Security advisories are for published vulnerabilities, not per-repo findings.