When CI build runs through, the resulting apt/yum repos should be directly available for installations (eg. just add sources.list entry/key to your machine and fire away).
Describe the solution you'd like
The requirements are not entirely trivial:
Need a stable signing key: for now the keyring is generated on-demand and cached on gh (when the cache expires, a new one is generated). It's in no way meant to provide security, just to let the repo builder run through. (an actual repo maintainer would run the tool on his own machine, with his own keyring). Obviously that's painful, when repos should be built and hosted on gh.
Need to separate branches: actual repo configs are usually done in separate branches, so these somehow need to be reflected in the repo hosting schema.
Need to separate configs: there can be multiple target configs, usually using the same pool names, so these somehow need to be separated by the repo hosting schema.
What is the problem you're trying to solve
When CI build runs through, the resulting apt/yum repos should be directly available for installations (eg. just add sources.list entry/key to your machine and fire away).
Describe the solution you'd like
The requirements are not entirely trivial:
Additional context
No response