Add Gitea Actions CI and tag releases
CI / check (push) Canceled after 0s

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
yuriy.pandClaude Opus 5.5 committed 2026-10-25 12:05:25 +06:00
1 parent 07e12eec6a
commit 4848e6bed6
3 files changed
+220

No files matched your search

+25
View File
@@ -82,6 +82,31 @@ changing the sources:
- `python3 tool/make_icon.py assets/icon/musyx.png` redraws the icon itself.
- The fonts are copied by hand from `assets/fonts` to `res/font` (lower-case names).
### CI and releases
Gitea Actions runs `.gitea/workflows/ci.yml` on every push to `main` and every pull request:
the unit tests, Lint and debug builds of both apps. A failed run keeps the reports as an
artifact.
To release, bump `versionName` and `versionCode` in `tv/build.gradle.kts` and/or
`mobile/build.gradle.kts`, commit, and push a tag named `v<phone>-tv<tv>`:
```bash
git tag v0.1.3-tv0.1.8 && git push origin v0.1.3-tv0.1.8
```
`.gitea/workflows/release.yml` then checks that the tag matches the versions, builds both
apps signed with the release key, and attaches `tv-release.apk` and `mobile-release.apk` to
the tag's release. It creates the release if there isn't one yet, with the commit subjects
since the previous tag as its notes; a release written by hand beforehand keeps its notes.
Running the workflow by hand from the Actions tab is a dry run that keeps the signed APKs as
an artifact instead of publishing.
The key comes from four repository secrets (Settings, Actions, Secrets):
`RELEASE_KEYSTORE_BASE64` (the keystore, from `base64 -i musyx-key.keystore`),
`RELEASE_STORE_PASSWORD`, `RELEASE_KEY_ALIAS` and `RELEASE_KEY_PASSWORD`, the same values
`keystore.properties` holds locally.
## Layout
- `core/`: what the apps share (`it.panov.musyx`), under `core/src/main/java/it/panov/musyx`: