dtourolle 10d77f1380 ci: publish a test APK as a pre-release for outside testers ...

Gitea artifacts need an account with read access to download, which makes
them useless for handing a build to someone outside the project -- the
actual reason a test APK gets built in the first place.

An optional publish input attaches the APK to a pre-release instead,
whose assets are a plain public URL on a public repo. No merge to master,
no MR, no version tag, and the tester needs no account.

Safe from a feature branch on two counts. The tag is test-<branch> rather
than v*, and only v* triggers build-release.yml, so nothing else reacts
to it. And it cannot reach existing users: the desktop updater reads a
static latest.json from the updater branch, not the release list.

Re-dispatching the same branch replaces the APK on the existing
pre-release rather than accumulating one release per attempt.

2026-08-30 20:06:40 +02:00

..

ISSUE_TEMPLATE

docs: add the governance and CI-operations files the project never had

2026-08-21 18:45:40 +02:00

workflows

ci: publish a test APK as a pre-release for outside testers

2026-08-30 20:06:40 +02:00

PULL_REQUEST_TEMPLATE.md

docs: add the governance and CI-operations files the project never had

2026-08-21 18:45:40 +02:00