Files
starter-workflows/code-scanning
Thomas Boop 1d9d6d7fb0 Update Actions to node16 (#1469)
* update actions

* address merge conflicts

* fix java updates

* update github script

* update cache to v3

Co-authored-by: Bishal Prasad <bishal-pdmsft@github.com>
2022-03-28 22:40:48 +05:30
..
2022-03-07 09:27:40 -08:00
2022-03-28 22:40:48 +05:30
2022-02-14 15:19:56 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2021-04-17 14:08:56 -04:00
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30
2022-03-28 22:40:48 +05:30

Code Scanning Workflows

GitHub code scanning is a developer-first, GitHub-native approach to easily find security vulnerabilities before they reach production. Before you can configure code scanning for a repository, you must enable code scanning by adding a GitHub Actions workflow to the repository. For more information, see Setting up code scanning for a repository.