robojerk/codeql-action

Mark invalid external repo specifiers as configuration error

Browse source 
This is a workaround — the proper fix is to better separate out user input vs the Action in `database init` so we can better attribute configuration errors.
This commit is contained in:
Henry Mercer 2025-01-10 20:41:24 +00:00
parent 87fc816d25
commit fe593c34e6
3 changed files with 13 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

6
src/cli-errors.ts
View file

@ -124,6 +124,7 @@ export enum CliConfigErrorCategory {
IncompatibleWithActionVersion = "IncompatibleWithActionVersion",
InitCalledTwice = "InitCalledTwice",
InvalidConfigFile = "InvalidConfigFile",
InvalidExternalRepoSpecifier = "InvalidExternalRepoSpecifier",
InvalidSourceRoot = "InvalidSourceRoot",
MavenBuildFailed = "MavenBuildFailed",
NoBuildCommandAutodetected = "NoBuildCommandAutodetected",
@ -188,6 +189,11 @@ export const cliErrorsConfig: Record<
new RegExp("The supplied config file is empty"),
],
},
[CliConfigErrorCategory.InvalidExternalRepoSpecifier]: {
cliErrorMessageCandidates: [
new RegExp("Specifier for external repository is invalid"),
],
},
// Expected source location for database creation does not exist
[CliConfigErrorCategory.InvalidSourceRoot]: {
cliErrorMessageCandidates: [new RegExp("Invalid source root")],