From 16a9187f58445fc00a0a29325d57e360d5f68440 Mon Sep 17 00:00:00 2001 From: Marius Date: Fri, 4 Dec 2020 17:54:43 +0200 Subject: [PATCH] Updated wording to reflect behaviour (#745) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Joakim Sørensen --- docs/add-ons/publishing.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/add-ons/publishing.md b/docs/add-ons/publishing.md index 50ad22b2..e06d01ff 100644 --- a/docs/add-ons/publishing.md +++ b/docs/add-ons/publishing.md @@ -30,7 +30,7 @@ All add-ons are simple docker containers. Inside your add-on `config.json` you s You can use `{arch}` inside the image name to support multiple architectures with one (1) configuration file. It will be replaced with the architecture of the user when we load the image. If you use `Buildargs` you can use the `build.json` to overwrite our default args. -Home Assistant assumes that the `master` branch of your add-on repository matches the latest tag on Docker Hub. When you're building a new version, it's suggested that you use another branch, ie `build` or do it with a PR on GitHub. After you push the add-on to [Docker Hub](https://hub.docker.com/), you can merge this branch to master. +Home Assistant assumes that the default branch of your add-on repository matches the latest tag on Docker Hub. When you're building a new version, it's suggested that you use another branch, ie `build` or do it with a PR on GitHub. After you push the add-on to [Docker Hub](https://hub.docker.com/), you can merge this branch to master. ## Custom Add-ons