Fix problem matcher registration (#32)

Bumps [dessant/lock-threads](https://github.com/dessant/lock-threads) from 2.0.3 to 2.1.1.
- [Release notes](https://github.com/dessant/lock-threads/releases)
- [Changelog](https://github.com/dessant/lock-threads/blob/master/CHANGELOG.md)
- [Commits](https://github.com/dessant/lock-threads/compare/v2.0.3...v2.1.1)

---
updated-dependencies:
- dependency-name: dessant/lock-threads
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

.github/labels.yml

@@ -25,9 +25,6 @@
 - name: "maintenance"
   color: 2af79e
   description: "Generic maintenance tasks."
-- name: "chore"
-  color: 2af79e
-  description: "Generic chore."
 - name: "ci"
   color: 1d76db
   description: "Work that improves the continue integration."

.github/release-drafter.yml

@@ -21,7 +21,7 @@ categories:
       - "performance"
   - title: "🧰 Maintenance"
     labels:
-      - "chore"
+      - "maintenance"
       - "ci"
   - title: "📚 Documentation"
     labels:

.github/workflows/labels.yaml

@@ -18,6 +18,6 @@ jobs:
       - name: ⤵️ Check out code from GitHub
         uses: actions/checkout@v2.3.4
       - name: 🚀 Run Label Syncer
-        uses: micnncim/action-label-syncer@v1.2.0
+        uses: micnncim/action-label-syncer@v1.3.0
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/lint.yaml

@@ -2,20 +2,20 @@
 name: Lint
 
 # yamllint disable-line rule:truthy
-on: [push, pull_request]
+on: [push, pull_request, workflow_dispatch]
 
 jobs:
-  build:
-    name: 🧹 yamllint
+  yamllint:
+    name: yamllint
     runs-on: ubuntu-latest
     steps:
       - name: ⤵️ Check out code from GitHub
         uses: actions/checkout@v2.3.4
       - name: 🚀 Run yamllint
-        uses: frenck/action-yamllint@v1.0.1
+        uses: frenck/action-yamllint@v1.1
 
   prettier:
-    name: 🧹 Prettier
+    name: Prettier
     runs-on: ubuntu-latest
     steps:
       - name: ⤵️ Check out code from GitHub

.github/workflows/lock.yaml

@@ -12,7 +12,7 @@ jobs:
     name: 🔒 Lock closed issues and PRs
     runs-on: ubuntu-latest
     steps:
-      - uses: dessant/lock-threads@v2.0.3
+      - uses: dessant/lock-threads@v2.1.1
         with:
           github-token: ${{ github.token }}
           issue-lock-inactive-days: "30"

.github/workflows/release-drafter.yaml

@@ -13,6 +13,6 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: 🚀 Run Release Drafter
-        uses: release-drafter/release-drafter@v5.13.0
+        uses: release-drafter/release-drafter@v5.15.0
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/stale.yaml

@@ -13,7 +13,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: 🚀 Run stale
-        uses: actions/stale@v3.0.14
+        uses: actions/stale@v3.0.19
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
           days-before-stale: 30

README.md

@@ -52,7 +52,7 @@ By default, this GitHub Action will use the root folder as the Home Assistant
 Core configuration folder. If you store your Home Assistant configuration in a
 subfolder, the `path` argument can be used to inform the Action about that.
 
-For example, if you configuration is in the `config` folder:
+For example, if your configuration is in the `config` folder:
 
 ```yaml
 - name: 🚀 Run Home Assistant Core Configuration Check
@@ -71,7 +71,7 @@ This GitHub Action offers a way around that, but using a fake secrets file.
 To use this, add a fake secrets file to your repository (e.g.,
 `fakesecrets.yaml`) and make sure the content is the same as your real
 `secrets.yaml` (with, of course, fake credentials/data). The GitHub Action
-will use this file during checking your configuration.
+will use this file while checking your configuration.
 
 For example, if you fake secrets file is `fakesecrets.yaml`:
 
@@ -91,7 +91,7 @@ folder.
 
 If the `.HA_VERSION` file is found, the version in that file is used. If
 the `.HA_VERSION` file is not found; the Action will use the latest stable
-version of Home Assistant to test your configuration with.
+version of Home Assistant to test your configuration.
 
 However, you can specify/override any version you like to check against,
 for example, check with Home Assistant Core `2021.1.0`:
@@ -104,7 +104,7 @@ for example, check with Home Assistant Core `2021.1.0`:
 ```
 
 Alternatively, you can also use `stable`, `beta` or `dev` to run against
-latest versions of those stability channels.
+the latest versions of those stability channels.
 
 ```yaml
 - name: 🚀 Run Home Assistant Core Configuration Check
@@ -145,6 +145,9 @@ The following repositories are using this GitHub Action, and thus provide
 you with some real-world uses of this GitHub Action.
 
 - [Frenck's Home Assistant Configuration](https://github.com/frenck/home-assistant-config)
+- [Klaasnicolaas - Student Home Assistant Configuration](https://github.com/klaasnicolaas/Student-homeassistant-config)
+- [Metbril's :sunglasses: Home Assistant Configuration](https://github.com/metbril/home-assistant-config)
+- [ntilley905's Home Assistant Configuration](https://github.com/ntilley905/hass)
 
 Are you using this GitHub Action? Feel free to open up a PR to add your
 configuration to this list 😍
@@ -189,21 +192,21 @@ as long as it is version 1.
 
 ```yaml
 - name: 🚀 Run Home Assistant Configuration Check
-  uses: frenck/action-home-assistant@v1.1
+  uses: frenck/action-home-assistant@v1
 ```
 
 ### Automatically update using Dependabot
 
-The advantage of locking against a more specific version, is that it prevent
+The advantage of locking against a more specific version, is that it prevents
 surprises if an issue or breaking changes were introduced in a newer release.
 
 The disadvantage of being more specific, is that it requires you to keep things
 up to date. Fortunately, GitHub has a tool for that, called: Dependabot.
 
 Dependabot can automatically open a pull request on your repository to update
-this action for you. You can instantly see if the new version works (as the
+this Action for you. You can instantly see if the new version works (as the
 pull request shows the success or failure status) and you can decide to
-merge it in but hitting the merge button. Quick, easy and always up2date.
+merge it in by hitting the merge button. Quick, easy and always up2date.
 
 To enable Dependabot, create a file called `.github/dependabot.yaml`:
 

action.yaml

@@ -86,7 +86,13 @@ runs:
         fi
         echo "::set-output name=version::${version}"
 
-        docker pull "homeassistant/home-assistant:${version}"
+        docker pull -q "homeassistant/home-assistant:${version}"
+
+    - name: 🏗 Register Home Assistant problem matcher
+      shell: bash
+      run: |
+        matcher="${{ github.action_path }}/matcher.json"
+        echo "::add-matcher::${matcher}"
 
     - name: 🚀 Run Home Assistant Configuration Check
       shell: bash

matcher.json

@@ -0,0 +1,25 @@
+{
+  "problemMatcher": [
+    {
+      "owner": "homeassistant-warnings",
+      "pattern": [
+        {
+          "regexp": "^(WARNING):(.*)$",
+          "severity": 1,
+          "message": 2
+        }
+      ]
+    },
+    {
+      "owner": "homeassistant-invalid-config",
+      "pattern": [
+        {
+          "regexp": "(Invalid config for .*) \\(See (.*)(?::|, line )(\\d|\\?)\\)",
+          "file": 2,
+          "line": 3,
+          "message": 1
+        }
+      ]
+    }
+  ]
+}