pr.yaml → Triggered on PR against master — lints, builds, and tests (no push)
tag.yaml → Triggered on push to master — bumps version and pushes git tag
This follows the same split pattern applied to web/docker-ttrss.
Split the monolithic `docker-build.yaml` into separate trigger-based workflows:
- **main.yaml** → Triggered on push to `master` — builds, tests, and pushes `jcabillot/rssbridge:latest`
- **cron.yaml** → Triggered nightly (`0 0 * * *`) — rebuilds and pushes `jcabillot/rssbridge:nightly`
- **pr.yaml** → Triggered on PR against `master` — lints, builds, and tests (no push)
- **tag.yaml** → Triggered on push to `master` — bumps version and pushes git tag
This follows the same split pattern applied to `web/docker-ttrss`.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Split the monolithic
docker-build.yamlinto separate trigger-based workflows:master— builds, tests, and pushesjcabillot/rssbridge:latest0 0 * * *) — rebuilds and pushesjcabillot/rssbridge:nightlymaster— lints, builds, and tests (no push)master— bumps version and pushes git tagThis follows the same split pattern applied to
web/docker-ttrss.