Sak code ql - #4127
Closed
beer-sakthai wants to merge 614 commits into
Closed
Conversation
There is no more (non-test) Python code left to analyse, so CodeQL analysis would fail now
… in `src/util.ts` dependencies
Add repository property for `tools` input
Promote `AllowToolcacheInput` feature
Co-authored-by: Mads Navntoft <navntoft@github.com>
Ignore configuration file repo property for unsupported analysis kinds
Convert last remaining Python CI scripts to TypeScript
Use in `init` and `setup-codeql` actions
The `start-proxy` step precedes `init` in Default Setup
Bumps the npm-minor group with 2 updates in the / directory: [js-yaml](https://github.com/nodeca/js-yaml) and [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint). Updates `js-yaml` from 5.3.0 to 5.4.0 - [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md) - [Commits](nodeca/js-yaml@5.3.0...5.4.0) Updates `typescript-eslint` from 8.67.0 to 8.68.0 - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.68.0/packages/typescript-eslint) --- updated-dependencies: - dependency-name: js-yaml dependency-version: 5.4.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: npm-minor - dependency-name: typescript-eslint dependency-version: 8.68.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: npm-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Bumps [eslint-plugin-jsdoc](https://github.com/gajus/eslint-plugin-jsdoc) from 62.9.0 to 64.2.1. - [Release notes](https://github.com/gajus/eslint-plugin-jsdoc/releases) - [Commits](gajus/eslint-plugin-jsdoc@v62.9.0...v64.2.1) --- updated-dependencies: - dependency-name: eslint-plugin-jsdoc dependency-version: 64.2.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Add support for Linux Arm64 runners
…lint-plugin-jsdoc-64.2.1 Bump eslint-plugin-jsdoc from 62.9.0 to 64.2.1
…owserslist-4.28.8 Bump browserslist from 4.24.2 to 4.28.8
…m-minor-21ac56865f Bump the npm-minor group across 1 directory with 2 updates
…dot-github/workflows/actions/setup-java-6.0.0 Bump actions/setup-java from 5.7.0 to 6.0.0 in /.github/workflows
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
- Analyze all languages CodeQL supports on Linux Arm64 (except Swift, which is macOS only) in the Linux Arm64 check, building the compiled ones via the shared multi-language-repo build.sh - De-duplicate the check's language list via a shared LANGUAGES env var used by both the init input and the assert loop - Fix CHANGELOG tense: "download" -> "downloads" Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…tokit/plugin-rest-endpoint-methods-18.0.0 Bump @octokit/plugin-rest-endpoint-methods from 17.0.0 to 18.0.0
Log a success line for each language database found in the Linux Arm64 PR check. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…rif-upload-flake Don't upload the ESLint SARIF from merge queue refs
…omments Analyze all supported languages in the Linux Arm64 check
Don't record an overlay status when the job was cancelled
…kill chore: add codeql-action maintainer skill
Member
|
Hi @beer-sakthai, Thanks for your interest in this project. If you'd like to contribute, please make sure that you read the CONTRIBUTION guidelines and, in particular, make sure that your pull requests have a clear title, description, and scope. I will close this PR since it doesn't meet those criteria. |
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
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.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Workflow types:
dynamicworkflows (Default Setup, Code Quality, ...).Products:
analysis-kinds: code-scanning.analysis-kinds: code-quality.upload-sarifaction.Environments:
github.comand/or GitHub Enterprise Cloud with Data Residency.How did/will you validate this change?
.test.tsfiles).pr-checks).If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist