-
I’ve read about custom problem matchers, but it seems like some program output (ESLint, for example) is already picked up as errors in check logs, and shows up as a per-line annotation in the PR changed files screen. Which problem matchers are enabled by default? Rather than going to the effort of writing a custom matcher, I’d like to tailor the output of my job to fit with existing matchers. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Interesting question. I’m not sure if this is active:
actions/runner/blob/be9632302ceef50bfb36ea998cea9c94c75e5d4d/src/Runner.Plugins/Repository/v1.1/GitSourceProvider.cs#L39-L49 My guess is that for most repositories, most of the time, this is active:
actions/checkout/blob/25a956c84d5dd820d28caab9f86b8d183aeeff3d/dist/problem-matcher.json#L2-L12 if you use actions/setup-python, you probably get this:
actions/setup-python/blob/a1121449a217580167611672a6c61b4cf314e0f2/.github/python.json#L2-L17 If you use setup-node, you probably get this:
actions/setup-node/blob/5c355be17065acf11598c7a9bb47112fbcf2bbdc/.github/tsc.json#L2-L17 and this:
actions/setup-node/blob/5c355be17065acf11598c7a9bb47112fbcf2bbdc/.github/eslint-compact.json#L2-L17 and this:
actions/setup-node/blob/5c355be17065acf11598c7a9bb47112fbcf2bbdc/.github/eslint-stylish.json#L2-L21 via:
actions/setup-node/blob/25316bbc1f10ac9d8798711f44914b1cf3c4e954/src/main.ts#L59-L64 and setup-go:
actions/setup-go/blob/3b4dc6cbed1779f759b9c638cb83696acea809d1/matchers.json#L2-L15 Results extracted from:
Build software better, togetherGitHub is where people build software. More than 65 million people use GitHub to discover, fork, and contribute to over 200 million projects. |
Beta Was this translation helpful? Give feedback.
Interesting question.
I’m not sure if this is active:
actions/runner/blob/be9632302ceef50bfb36ea998cea9c94c75e5d4d/src/Runner.Plugins/Repository/v1.1/GitSourceProvider.cs#L39-L49