actions: main -> gitea-pages branch #3

New Issue

djmil · 2024-06-26T22:08:09+02:00

djmil commented

2024-06-26 22:08:09 +02:00

Use Gitea Actions to generate gitea-pages branch from commits (PRs?) to main:

Since Gitea actions are similar to GitHub actions, this folder can be used as a starting point
Docker compose for Gitea act_runner
Resulting branch shall look something like this

Use Gitea Actions to generate `gitea-pages` branch from commits (PRs?) to `main`: - [x] Since Gitea actions are [similar](https://docs.gitea.com/usage/actions/overview) to GitHub actions, this [folder](https://github.com/emilk/eframe_template/tree/main/.github/workflows) can be used as a starting point - [ ] Docker [compose](https://docs.gitea.com/usage/actions/act-runner#set-up-the-runner-using-docker-compose) for Gitea `act_runner` - [ ] Resulting branch shall look something like [this](https://github.com/emilk/eframe_template/tree/gh-pages)

djmil added this to the pages milestone 2024-06-26 22:19:24 +02:00

djmil added a new dependency 2024-07-10 21:49:08 +02:00

#5 rust dev container

djmil added the

discard

label 2024-08-30 22:33:31 +02:00

djmil commented

2024-08-30 22:33:31 +02:00

At the moment i see no real added value in setting up gitea-actions for the sole purpose of publishing wasm32 build target. This can be easily done via ./wasm32/build.sh script.

At the moment i see no real added value in setting up `gitea-actions` for the sole purpose of publishing `wasm32` build target. This can be easily done via `./wasm32/build.sh` script.

djmil removed a dependency 2024-08-30 22:34:12 +02:00

#5 rust dev container

djmil closed this issue

2024-08-30 22:34:15 +02:00

Sign in to join this conversation.