yalan2ny/Patch 1 #2892
Open
yalan2ny/Patch 1 #2892
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Update CODEOWNERS
Update all Pages workflows to `actions/cache@v4` for `node20` compliance
removing extra whitespace
Update dependency-review.yml actions/checkout version, add common with: options, and add comments for dependency submission
- Bump version hashes to use `v3.0.0` of Gradle action - Bump to Node20-compatible versions of `actions/checkout` and `actions/setup-java` - Replace uses of `gradle/gradle-build-action` with `gradle/actions/setup-gradle` - Split "Setup Gradle" step out of "Run Gradle" steps - Add separate Job using `gradle/actions/dependency-submission` (flagged as optional) - Bump to setup JDK 17
- Remove "optional" flag from dependency-submission - Add example of running without Gradle wrapper - Link to action docs
Update for `gradle/actions@v3.0.0` release
* Update soos-dast-scan.yml * use major version syntax * code review * lint * Update soos-dast-scan.yml
also gave the workflow the appropriate permissions required, pull-requests: write
begone, whitespace Co-authored-by: Chad Bentz <1760475+felickz@users.noreply.github.com>
Changing default behavior to include comment summary in PR
Code Scanning shouldn't own `dependency-review.yml`
Usage as described in https://github.com/rubysec/bundler-audit#readme
As recommended in https://github.com/ruby/setup-ruby#setup-ruby
- Bump version hashes to use `gradle/actions/setup-gradle@v3.1.0` - Bump version hash to use `gradle/actions/dependency-submission@v3.1.0`
Update for `gradle/actions@v3.1.0` release
Co-authored-by: Henry Mercer <henrymercer@github.com>
Co-authored-by: Henry Mercer <henrymercer@github.com>
* Update dotnet.yml Updating versions * Update dotnet-desktop.yml Bumping versions * Update ci/dotnet-desktop.yml Co-authored-by: Alexis Abril <alexisabril@github.com> --------- Co-authored-by: Alexis Abril <alexisabril@github.com>
ab1d87dfccc5a0ffab88be3aaac6ffe35c10d6cd
Merging black-duck-security-scan template
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>
Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Scorecard currently has experimental support for the `pull_request` trigger, so we want to allow analysis to be run for it in the future. Signed-off-by: Spencer Schrock <sschrock@google.com>
Code Scanning: bandit to latest hash
Update Fortify starter workflow
fix: Scorecard artifact upload and version bump
…s/actions/cache-4 Bump actions/cache from 3 to 4
…RESPONSE variable
…iew-workflow Add summary preview workflow
Remove preview label from summary.properties.json
Pull request
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pre-requisites
Please note that at this time we are only accepting new starter workflows for Code Scanning. Updates to existing starter workflows are fine.
Tasks
For all workflows, the workflow:
.ymlfile with the language or platform as its filename, in lower, kebab-cased format (for example,docker-image.yml). Special characters should be removed or replaced with words as appropriate (for example, "dotnet" instead of ".NET").GITHUB_TOKENso that the workflow runs successfully.For CI workflows, the workflow:
cidirectory.ci/properties/*.properties.jsonfile (for example,ci/properties/docker-publish.properties.json).pushtobranches: [ $default-branch ]andpull_requesttobranches: [ $default-branch ].releasewithtypes: [ created ].docker-publish.yml).For Code Scanning workflows, the workflow:
code-scanningdirectory.code-scanning/properties/*.properties.jsonfile (for example,code-scanning/properties/codeql.properties.json), with properties set as follows:name: Name of the Code Scanning integration.creator: Name of the organization/user producing the Code Scanning integration.description: Short description of the Code Scanning integration.categories: Array of languages supported by the Code Scanning integration.iconName: Name of the SVG logo representing the Code Scanning integration. This SVG logo must be present in theiconsdirectory.pushtobranches: [ $default-branch, $protected-branches ]andpull_requesttobranches: [ $default-branch ]. We also recommend ascheduletrigger ofcron: $cron-weekly(for example,codeql.yml).Some general notes:
actionsorganization, or