Pull HASS image quietly (#25)

This will eliminate a lot of unnecessary log spam.

.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/additional-tags.yaml

@@ -0,0 +1,22 @@
+---
+name: Additional Tags
+
+# yamllint disable-line rule:truthy
+on:
+  push:
+    tags:
+      - v[0-9]+.[0-9]+.[0-9]+
+  release:
+    types:
+      - published
+  workflow_dispatch:
+
+jobs:
+  additional-tags:
+    name: 🏷 Additional Tags
+    runs-on: ubuntu-latest
+    steps:
+      - name: ⤵️ Check out code from GitHub
+        uses: actions/checkout@v2.3.4
+      - name: 🚀 Run Release Tracker
+        uses: vweevers/additional-tags-action@v1.0.0

.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:
+  yamllint:
-    name: 🧹 yamllint
+    name: yamllint
     runs-on: ubuntu-latest
     steps:
       - name: ⤵️ Check out code from GitHub
-        uses: actions/checkout@v2
+        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/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.18
         with:
           repo-token: ${{ secrets.GITHUB_TOKEN }}
           days-before-stale: 30

.github/workflows/test.yaml

@@ -2,7 +2,7 @@
 name: Test
 
 # yamllint disable-line rule:truthy
-on: [push, pull_request]
+on: [push, pull_request, workflow_dispatch]
 
 jobs:
   build:

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
@@ -139,6 +139,18 @@ jobs:
           version: "${{ matrix.version }}"
 ```
 
+## Real-world examples
+
+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)
+
+Are you using this GitHub Action? Feel free to open up a PR to add your
+configuration to this list 😍
+
 ## Changelog & Releases
 
 This repository keeps a change log using [GitHub's releases][releases]
@@ -152,6 +164,63 @@ based on the following:
 - `MINOR`: Backwards-compatible new features and enhancements.
 - `PATCH`: Backwards-compatible bugfixes and package updates.
 
+## Versions & Updating
+
+You can specify which version of this GitHub Action your workflow should use.
+And even allowing for using the latest major or minor version.
+
+For example; this will use release `v1.1.1` of a GitHub Action:
+
+```yaml
+- name: 🚀 Run Home Assistant Configuration Check
+  uses: frenck/action-home-assistant@v1.1.1
+```
+
+While the following example, will use the `v1.1.x` minor release, for example
+if `v1.1.2` is the latest releases (starting with `v1.1`), this will run
+`v1.1.2`:
+
+```yaml
+- name: 🚀 Run Home Assistant Configuration Check
+  uses: frenck/action-home-assistant@v1.1
+```
+
+As in the examples throughout the documentation, the following example is
+locked on major version, meaning any `v1.x.x` latest version will be used,
+as long as it is version 1.
+
+```yaml
+- name: 🚀 Run Home Assistant Configuration Check
+  uses: frenck/action-home-assistant@v1
+```
+
+### Automatically update using Dependabot
+
+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
+pull request shows the success or failure status) and you can decide to
+merge it in by hitting the merge button. Quick, easy and always up2date.
+
+To enable Dependabot, create a file called `.github/dependabot.yaml`:
+
+```yaml
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: daily
+```
+
+Your all set! Dependabot will now check (and update) your GitHub actions
+every day. 🤩
+
 ## Contributing
 
 This is an active open-source project. We are always open to people who want to

action.yaml

@@ -86,7 +86,7 @@ runs:
         fi
         echo "::set-output name=version::${version}"
 
-        docker pull "homeassistant/home-assistant:${version}"
+        docker pull -q "homeassistant/home-assistant:${version}"
 
     - name: 🚀 Run Home Assistant Configuration Check
       shell: bash