Files
starter-workflows/code-scanning
Spencer Schrock f70f9c8252 bump action versions to latest to resolve issues
1. Scorecard update v2.4.1 was released, which includes months of bug
   fixes and a new `file_mode` input to address a .gitattributes bug.
2. Bumped actions/upload-artifact to the v4 branch. This was previously
   kept at  v3 as GHES doesn't support v4, but github.com no longer
   supports v3: as uploads return the following error "Create Artifact
   Container failed: The artifact name JSON file is not valid."

  Signed-off-by: Spencer Schrock <sschrock@google.com>
2025-02-24 11:27:23 -07:00
..
2025-02-10 11:43:15 +06:00
2025-01-13 20:52:25 -05:00
2025-01-14 13:13:27 -05:00
2024-09-11 11:12:06 -07:00
2024-06-28 15:56:30 +03:00
2024-06-28 15:56:30 +03:00
2021-04-17 14:08:56 -04:00
2022-12-08 06:10:22 +00:00

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.