# Inviting testers for Git forge usecases **URL:** \ **Category:** Project Discussion\ **Tags:** git-forge-future, fesco, package-maintainers, engineering, release-engineering-team, council, quality-team\ **Created:** [August 20, 2024, 8:12am UTC](https://discussion.fedoraproject.org/t/inviting-testers-for-git-forge-usecases/129016 "2024-08-20T08:12:38Z")\ **Posts on this page:** 1\ **Showing post:** 80
**Author:** ![siosm](https://sea1.discourse-cdn.com/fedoraproject/user_avatar/discussion.fedoraproject.org/siosm/32/79_2.png) [@siosm](https://discussion.fedoraproject.org/u/siosm)\ **Post date:** [October 22, 2024, 12:35pm UTC](https://discussion.fedoraproject.org/t/inviting-testers-for-git-forge-usecases/129016/80 "2024-10-22T12:35:32Z")
You can split your template however you choose. Here is an example for a KDE application: - [.gitlab-ci.yml · master · Graphics / Okular · GitLab](https://invent.kde.org/graphics/okular/-/blob/master/.gitlab-ci.yml?ref_type=heads) - [Sysadmin / CI Utilities · GitLab](https://invent.kde.org/sysadmin/ci-utilities) For example, all applications in KDE GitLab CI are built as Flatpak from the same template: - [gitlab-templates/flatpak.yml · master · Sysadmin / CI Utilities · GitLab](https://invent.kde.org/sysadmin/ci-utilities/-/blob/master/gitlab-templates/flatpak.yml?ref_type=heads) We could certainly do the same for RPM packaging. Forgejo Actions are similar to GitHub Actions ([Forgejo Actions user guide | Forgejo – Beyond coding. We forge.](https://forgejo.org/docs/latest/user/actions/)) and we could indeed create a set of Actions that do the RPM packaging and testing in a similar fashion to what’s done today in Zuul/Testing Farm. Or we could also plug the existing CI (Zuul/Testing Farm) to it to get up to speed quicker. I regularly use both GitLab CI & GitHub Actions and they both have their advantages and downsides. --- _[View the full topic](https://discussion.fedoraproject.org/t/inviting-testers-for-git-forge-usecases/129016)._