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
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ See the [releases page](https://github.com/github/codeql-action/releases) for th
4
4
5
5
## [UNRELEASED]
6
6
7
-
- Organizations can now create a custom repository property with the name `github-codeql-tools` to set the default CodeQL CLI tools value for their repositories. For more information, see [Managing custom properties for repositories in your organization](https://docs.github.com/en/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization), [Repository properties for Code Scanning](https://docs.github.com/en/code-security/concepts/code-scanning/repository-properties) and [Customizing your advanced setup for code scanning](https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning).
7
+
- Organizations can now create a custom repository property with the name `github-codeql-tools` to set the default CodeQL CLI tools value for dynamic workflows. If a workflow provides an explicit `tools:` input, that input takes precedence. For more information, see [Managing custom properties for repositories in your organization](https://docs.github.com/en/organizations/managing-organization-settings/managing-custom-properties-for-repositories-in-your-organization), [Repository properties for Code Scanning](https://docs.github.com/en/code-security/concepts/code-scanning/repository-properties) and [Customizing your advanced setup for code scanning](https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning).
Copy file name to clipboardExpand all lines: src/resolve-tools-input.ts
+10-1Lines changed: 10 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -7,15 +7,17 @@ import { Logger } from "./logging";
7
7
/**
8
8
* Resolves the effective tools input by combining the workflow input and repository properties.
9
9
* The explicit `tools` workflow input takes precedence. If none is provided,
10
-
* falls back to the repository property (if set).
10
+
* falls back to the repository property (if set and enabled for this workflow).
11
11
*
12
12
* @param toolsWorkflowInput - The value of the `tools` workflow input, if provided.
13
+
* @param allowRepositoryPropertyFallback - Whether the repository property fallback is enabled.
13
14
* @param repositoryProperties - The parsed repository properties.
14
15
* @param logger - Logger for outputting resolution messages.
15
16
* @returns The effective tools input value.
16
17
*/
17
18
exportfunctionresolveToolsInput(
18
19
toolsWorkflowInput: string|undefined,
20
+
allowRepositoryPropertyFallback: boolean,
19
21
repositoryProperties: RepositoryProperties,
20
22
logger: Logger,
21
23
): string|undefined{
@@ -26,6 +28,13 @@ export function resolveToolsInput(
26
28
returntoolsWorkflowInput;
27
29
}
28
30
31
+
if(!allowRepositoryPropertyFallback){
32
+
logger.info(
33
+
`No explicit tools input was provided. Ignoring '${RepositoryPropertyName.TOOLS}' repository property because it is only supported for dynamic workflows.`,
0 commit comments