From 10c9c4a1931c7493bc431f3ae9349320ba81fc0a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lukas=20Spie=C3=9F?= Date: Mon, 3 Apr 2023 13:18:33 +0000 Subject: [PATCH 1/3] Update install instructions for v2 --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 3af2b11..875bb76 100644 --- a/README.md +++ b/README.md @@ -13,7 +13,7 @@ This currently supports the `gcc` and `tty` formats. To enable the shellcheck problem matchers, simply add this Action as a step **before** running the actual `shellcheck` command: ```yaml -uses: lumaxis/shellcheck-problem-matchers@v1 +uses: lumaxis/shellcheck-problem-matchers@v2 run: shellcheck -f gcc *.sh ``` @@ -26,7 +26,7 @@ See the [actions tab](https://github.com/lumaxis/shellcheck-problem-matchers/act By default, this Action installs all available problem matchers but you can specify one of the available formats explicitly: ```yaml -uses: lumaxis/shellcheck-problem-matchers@v1 +uses: lumaxis/shellcheck-problem-matchers@v2 with: format: gcc # Available options are "gcc" or "tty" ``` From 58c414703ffe1d757f6238cb937b97e372cf724a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lukas=20Spie=C3=9F?= Date: Mon, 3 Apr 2023 13:27:04 +0000 Subject: [PATCH 2/3] Update to run CI on main branch --- .github/workflows/test.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml index 62e30dc..713c687 100644 --- a/.github/workflows/test.yml +++ b/.github/workflows/test.yml @@ -2,7 +2,7 @@ name: "Test shellcheck problem matchers" on: pull_request: push: - branches: [ master ] + branches: [ main ] jobs: lint: From 661aa03d95dea0dfba3a4a732ba4d9431bd6e2b1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lukas=20Spie=C3=9F?= Date: Mon, 3 Apr 2023 13:29:48 +0000 Subject: [PATCH 3/3] Update link in Readme --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f72bd61..0b691e8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,7 +2,7 @@ ## Testing problem matchers locally -Since GitHub Actions are functionally very similar to [VS Code's problem matchers](https://code.visualstudio.com/Docs/editor/tasks#_defining-a-problem-matcher) (outside of some [exceptions](https://github.com/actions/runner/blob/master/docs/adrs/0276-problem-matchers.md#where-we-diverge-from-vscode)), we can use VS Code locally to quickly test the matcher patterns. +Since GitHub Actions are functionally very similar to [VS Code's problem matchers](https://code.visualstudio.com/Docs/editor/tasks#_defining-a-problem-matcher) (outside of some [exceptions](https://github.com/actions/runner/blob/main/docs/adrs/0276-problem-matchers.md#where-we-diverge-from-vscode)), we can use VS Code locally to quickly test the matcher patterns. 1. Make sure VS Code `.vscode/tasks.json` file is in sync with actual problem matchers ```bash