GH-500 · Question #22
By default, where will secret scanning look in a repository in order to execute its job? Each correct answer presents part of the solution. (Choose three.)
The correct answer is C. selected files in the repository D. full commit history E. all branches. Secret scanning scans your entire Git history[D] on all branches [E] present in your GitHub repository for secrets, even if the repository is archived. GitHub will also periodically run a full Git history scan for new secret types in existing content in public repositories…
Question
By default, where will secret scanning look in a repository in order to execute its job? Each correct answer presents part of the solution. (Choose three.)
Options
- Aall files in the repository
- Bdependencies
- Cselected files in the repository
- Dfull commit history
- Eall branches
How the community answered
(29 responses)- A3% (1)
- B7% (2)
- C90% (26)
Explanation
Secret scanning scans your entire Git history[D] on all branches [E] present in your GitHub repository for secrets, even if the repository is archived. GitHub will also periodically run a full Git history scan for new secret types in existing content in public repositories where secret scanning is enabled [C, not A] when new supported secret types are added. Additionally, secret scanning scans: Descriptions and comments in issues Titles, descriptions, and comments, in open and closed historical issues. A notification is sent to the relevant partner when a historical partner pattern is detected. Titles, descriptions, and comments in pull requests Titles, descriptions, and comments in GitHub Discussions Wikis
Topics
Community Discussion
No community discussion yet for this question.