You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of using a bundled node_modules,
* Run `npm install` before performing various tasks
Change pr-checks to not be particularly picky about the generated
content because it will differ between different versions as everything
is bundled together.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1
Original file line number
Diff line number
Diff line change
@@ -28,6 +28,7 @@ No user facing changes.
28
28
29
29
- The CodeQL Action now downloads bundles compressed using Zstandard on GitHub Enterprise Server when using Linux or macOS runners. This speeds up the installation of the CodeQL tools. This feature is already available to GitHub.com users. [#2573](https://github.com/github/codeql-action/pull/2573)
30
30
- Update default CodeQL bundle version to 2.19.3. [#2576](https://github.com/github/codeql-action/pull/2576)
31
+
- The CodeQL Action is now faster to download by several seconds since `node_modules` are no longer included in this repository. [#2578](https://github.com/github/codeql-action/pull/2578)
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-9
Original file line number
Diff line number
Diff line change
@@ -17,20 +17,14 @@ Before you start, ensure that you have a recent version of node (16 or higher) i
17
17
18
18
### Common tasks
19
19
20
-
* Transpile the TypeScript to JavaScript: `npm run build`. Note that the JavaScript files are committed to git.
21
-
* Run tests: `npm run test`. You’ll need to ensure that the JavaScript files are up-to-date first by running the command above.
22
-
* Run the linter: `npm run lint`.
20
+
* Transpile the TypeScript to JavaScript: `npm run build`. Note that the bundled action files are committed to git.
21
+
* Run tests: `npm run test`. You’ll need to ensure that the `node_modules` are available and JavaScript files are up-to-date first by running the commands above.
22
+
* Run the linter: `npm run lint` (requires the first command).
23
23
24
24
This project also includes configuration to run tests from VSCode (with support for breakpoints) - open the test file you wish to run and choose "Debug AVA test file" from the Run menu in the Run panel.
25
25
26
26
You may want to run `tsc --watch` from the command line or inside of vscode in order to ensure build artifacts are up to date as you are working.
27
27
28
-
### Checking in compiled artifacts and `node_modules`
29
-
30
-
Because CodeQL Action users consume the code directly from this repository, and there can be no build step during an GitHub Actions run, this repository contains all compiled artifacts and node modules. There is a PR check that will fail if any of the compiled artifacts are not up to date. Compiled artifacts are stored in the `lib/` directory. For all day-to-day development purposes, this folder can be ignored.
31
-
32
-
Only run `npm install` if you are explicitly changing the set of dependencies in `package.json`. The `node_modules` directory should be up to date when you check out, but if for some reason, there is an inconsistency use `npm ci && npm run removeNPMAbsolutePaths` to ensure the directory is in a state consistent with the `package-lock.json`. Note that due to a macOS-specific dependency, this command should be run on a macOS machine. There is a PR check to ensure the consistency of the `node_modules` directory.
33
-
34
28
### Running the action
35
29
36
30
To see the effect of your changes and to test them, push your changes in a branch and then look at the [Actions output](https://github.com/github/codeql-action/actions) for that branch. You can also exercise the code locally by running the automated tests.
0 commit comments