Next to the global package repositories, you may create some of your own, if you need more control.

First, create a build webhook. You can select one or more distributions, major versions and hardware architectures combinations (for example fedora-35-x86_64). The packages will be built for all combinations and will be stored in separate repositories, transparently for your users.

To create a repository, you must be logged in and go to Settings - Packages - Repositories - Add, set a name, select the type (public or private) and press Add button.
To list the current repositories, go to Settings - Packages - Repositories.

Now, go to Settings - Packages - Subrepositories - Add, select a repository, set a name and press Add button. Suggested names for a subrepositories are: stable, testing, but any other names are allowed. You have a List submenu to see all subrepositories, as well.

When you push your commits, RocketGit must figure out in which package repository to put your packages.
It is basing this decision on the reference name (branch or tag).
For example, you may choose to store your packages generated from the release branch into stable package repository and from the tags starting with letter v (example v0.1) inside testing repository.
Go to Settings - Packages - Mappings - Add, set a priority, specify a regular expression for the git repository, another regular expression for the git reference and a destination package repository/subrepository.
When the build system evaluates into what repository to copy a package, the list of the mappings is ordered by priority and followed in increasing order. In this way, you may stop the evaluation of the rules at any point (by mapping to "No repo / no subrepo" destination).

At your next push, if a package is built, it will be copied to all matching repositories.

If you go to the git repository page, there is a submenu named Packages where you can find all repositories where the package is present, grouped by repository, distribution, major version and architecture.
You can also find the details about all past versions of a package, which worker built that package and when.
If you want to install that package on your machines, you can find there instructions on how to do it.

For private package repository, you may give rights to other users. For example, you may want to have a company repository from where all machines to get the updates of packages.