Skip to content

Commit 2bba796

Browse files
NiklasEialice-i-cecilerparrett
authored
Document usage of the workflows in your own project (#5)
* Document usage of the workflows in your own project * Typo Co-authored-by: Rob Parrett <robparrett@gmail.com> Co-authored-by: Alice Cecile <alice.i.cecile@gmail.com> Co-authored-by: Rob Parrett <robparrett@gmail.com>
1 parent 997b7ef commit 2bba796

1 file changed

Lines changed: 14 additions & 3 deletions

File tree

README.md

Lines changed: 14 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Bevy GitHub CI Template
22

3-
This repo show how to setup CI on a github project for Bevy.
3+
This repo show how to set up CI on a GitHub project for Bevy.
44

55
It creates two workflows:
66

@@ -11,7 +11,7 @@ It creates two workflows:
1111

1212
Definition: [.github/workflows/ci.yaml](./.github/workflows/ci.yaml)
1313

14-
This workflow runs on every commit to `main` branch, and on every PR targetting the `main` branch.
14+
This workflow runs on every commit to `main` branch, and on every PR targeting the `main` branch.
1515

1616
It will use rust stable on linux, with cache between different executions, those commands:
1717

@@ -51,11 +51,22 @@ git push --tags
5151

5252
### Result
5353

54-
A new release will be available in GitHub, with the archives per platform availble as downloadable assets.
54+
A new release will be available in GitHub, with the archives per platform available as downloadable assets.
5555

5656
The `git` commands above produced this release: [my-game-1.0](
5757
https://github.com/bevyengine/bevy_github_ci_template/releases/tag/my-game-1.0).
5858

59+
## Using the workflows in your own project
60+
61+
If you would like to use the GitHub workflows included here for your own project, there are a few things you might have to adapt:
62+
63+
1. The release workflow relies on the `index.html` file under `/wasm` for web builds
64+
2. Make sure that the env variable `binary` ([release.yaml](.github/workflows/release.yaml#L10)) matches the name of your binary
65+
3. In case your project doesn't have an `assets` folder
66+
1. Either create one and put a `.gitkeep` file in it to be able to push it
67+
2. Or remove the `cp -r assets` statements in the build jobs
68+
4. Adapt the used toolchain if you are using nightly
69+
5970
### Publish on itch.io
6071

6172
The release flow can be configured to push the releases to itch.io:

0 commit comments

Comments
 (0)