## ➹ New Feature implementation request <!-- Thank you for reporting an issue in our documentation 🙌 Before opening a new issue, please make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead. --> ### Is your feature request related to a problem? <!-- Please describe a clear and concise description of what the problem is. Use commmon user story patterns like https://en.wikipedia.org/wiki/User_story: - As a <role> I can <capability>, so that <receive benefit> - In order to <receive benefit> as a <role>, I can <goal/desire> - As <who> <when> <where>, I <want> because <why> For example... As a secureCodeBox user i'm always frustrated when [...] --> As secureCobeBox maintainer i would like to review PRs based on contributer forks with the project ci and all checks. ### Describe the solution you'd like <!-- Please describe a clear and concise description of what you want to happen. --> - Working with forks gets easier for contributors (less secrets/services to configure) - Working with forks gets easier for maintainers (enable the maintainer to see if CI is passing on a fork) - Increase stability - Fewer failures caused by flaky connections to DockerHub - Fewer failures caused by flaky timeouts (See #224 ) - Keep CI execution time to a minimum ### Describe alternatives you've considered <!-- Please describe a clear and concise description of any alternative solutions or features you've considered. --> ### Additional context <!-- Add any other context or screenshots about the feature request here. --> - https://docs.github.com/en/packages/guides/using-github-packages-with-github-actions - https://github.com/marketplace/actions/build-and-publish-docker-image-to-github-packages-registry - Docker Image Layer Caching: https://evilmartians.com/chronicles/build-images-on-github-actions-with-docker-layer-caching - Share Secrets to Forks: https://github.blog/2020-08-03-github-actions-improvements-for-fork-and-pull-request-workflows/ - Possible security Issues: https://securitylab.github.com/research/github-actions-preventing-pwn-requests/ - Using a local registry: https://stackoverflow.com/questions/63887031/build-docker-image-locally-in-github-actions-using-docker-build-push-action - Export Docker Images: https://docs.docker.com/engine/reference/commandline/export/. https://docs.docker.com/engine/reference/commandline/save/ - KIND Import Docker Images: https://kind.sigs.k8s.io/docs/user/quick-start#loading-an-image-into-your-cluster - https://docs.github.com/en/actions/guides/storing-workflow-data-as-artifacts See #476
➹ New Feature implementation request
Is your feature request related to a problem?
As secureCobeBox maintainer i would like to review PRs based on contributer forks with the project ci and all checks.
Describe the solution you'd like
Describe alternatives you've considered
Additional context
See #476