From 6ea1fade3961a1eb2f7e98b0aeb4aba9d04ca6ed Mon Sep 17 00:00:00 2001 From: Tunghsiao Liu Date: Fri, 13 Jan 2017 19:23:54 +0800 Subject: [PATCH] =?UTF-8?q?feat(post):=20add=20testing=20guide=20for=20?= =?UTF-8?q?=E2=80=9CGetting=20Started=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../_posts/note/2014-06-12-getting-started.md | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/_app/_posts/note/2014-06-12-getting-started.md b/_app/_posts/note/2014-06-12-getting-started.md index 6c9e4f45e..9d4b0aefd 100644 --- a/_app/_posts/note/2014-06-12-getting-started.md +++ b/_app/_posts/note/2014-06-12-getting-started.md @@ -42,3 +42,23 @@ $ grunt amsf-update ``` It checks the latest Almace Scaffolding build from GitHub and update core files automatically. Please keep in mind that if you changed some of the AMSF core files this action will **override** the changes you made. So it's recommended to keep your project under version control, you will be always be able to compare changes for Almace Scaffolding. + +## Using Beta Release + +By default, when you run `amsf-update` you will get updated files from `release` branch. However, I'm continuously working on Almace Scaffolding, so there may have testing branches you can try and give me feedback if you're interested. You can check the AMSF GitHub repository for available branches, and it's very easy to switch: + +```sh +$ grunt amsf-update --branch=feat/service-worker +``` + +The branch `master` is the one which is always available to checkout and also has the latest changes: + +```sh +$ grunt amsf-update --branch=master +``` + +If you messed up with the testing branch, don't worry, you can just run a normal update to revert them back: + +```sh +$ grunt amsf-update +```