From 2b0e71338c93769858c5362c83bef1c7a1744ebd Mon Sep 17 00:00:00 2001 From: Manoel Aranda Neto <5731772+marandaneto@users.noreply.github.com> Date: Thu, 1 Jul 2021 14:58:32 +0200 Subject: [PATCH 1/2] Mention release branch on README --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 4dc05da90..1575ef5a2 100644 --- a/README.md +++ b/README.md @@ -264,6 +264,8 @@ status of the respective git revision in GitHub, and then publish available artifacts to configured targets (for example, to GitHub and NPM in the case of Craft). +- Be sure that your [CI config.](https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#example-including-branches-and-tags) runs for `release/**` branches. + ## Configuration File: `.craft.yml` Project configuration for `craft` is stored in `.craft.yml` configuration file, From 466c62a43fa846b34849136acbb2b730bba01b32 Mon Sep 17 00:00:00 2001 From: Manoel Aranda Neto Date: Fri, 2 Jul 2021 09:34:47 +0200 Subject: [PATCH 2/2] add yaml example to allow release branches to be built --- README.md | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 1575ef5a2..5c95bb374 100644 --- a/README.md +++ b/README.md @@ -264,8 +264,6 @@ status of the respective git revision in GitHub, and then publish available artifacts to configured targets (for example, to GitHub and NPM in the case of Craft). -- Be sure that your [CI config.](https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#example-including-branches-and-tags) runs for `release/**` branches. - ## Configuration File: `.craft.yml` Project configuration for `craft` is stored in `.craft.yml` configuration file, @@ -997,6 +995,14 @@ Here is how you can integrate your GitHub project with `craft`: 1. Set up a workflow that builds your assets and runs your tests. Allow building release branches (their names follow `release/{VERSION}` by default, configurable through `releaseBranchPrefix`). + + ```yaml + on: + push: + branches: + - 'release/**' + ``` + 2. Use the official `actions/upload-artifact@v2` action to upload your assets. Here is an example config (step) of an archive job: