Skip to content

docs: Mention release/** branches on README #263

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BYK merged 2 commits into from
Jul 6, 2021
Merged

docs: Mention release/** branches on README #263

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2b0e713
Mention release branch on README
marandaneto Jul 1, 2021
466c62a
add yaml example to allow release branches to be built
marandaneto Jul 2, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -995,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:

Expand Down