New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Deployment: Security Hardening the Self-Hosted Runners #1

Open

CodeGat opened this issue Oct 16, 2023 · 0 comments

Labels

priority:medium type:feature

Contributor

CodeGat commented Oct 16, 2023

See https://access-nri.github.io/procedures-and-practices/technical/reproducibility_and_performance_testing_organisation/

Considerations

As an especially hardline stance, could we just restrict PRs/forks to members within ACCESS-NRI? Thus eliminating the possibility of bad actors?

References ACCESS-NRI/build-ci#5

CodeGat transferred this issue from ACCESS-NRI/build-ci

CodeGat added type:feature priority:blocker labels

CodeGat added priority:medium and removed priority:blocker labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment