All our modules related to developments that solves generic issues on Odoo, or that solve internal problems on Odoo Core, if something is here, maybe it is solving an issue in your company, try it and report what you see.
For security reasons, when tests are run from a fork, secrets are not availabe to the jobs [1], not even if the same secrets are configured in the fork. Unfortunately, We rely in such secrets in order for vxci to work properly, so it is able to connect to Quay.io, Orchest, etc.
To solve the avove, we are making tests to run directly in the target repo, but checking out the code submitted in the source repo. That way:
Security is preserved because actions will always be taken from the base repo, so if for instance someone submits a PR changing action's code, it will never be run
For security reasons, when tests are run from a fork, secrets are not availabe to the jobs [1], not even if the same secrets are configured in the fork. Unfortunately, We rely in such secrets in order for vxci to work properly, so it is able to connect to Quay.io, Orchest, etc.
To solve the avove, we are making tests to run directly in the target repo, but checking out the code submitted in the source repo. That way:
[1] https://docs.github.com/en/actions/security-guides/encrypted-secrets#using-encrypted-secrets-in-a-workflow