Consider allowing CI to always run the private layer
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 270
- Forks
- 123
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 3
Description
Description of feature
I think it's helpful to enable the private layer on all CI, even when PRs are opened by non-lab members. To prevent malicious access, we can set GHA to only run for collaborators after manual approval from a reviewer.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the repository's GitHub Actions CI configuration and how the private layer is currently enabled. Determine how manual approval for collaborator-triggered runs would work, then verify that approved runs access the private layer while unapproved runs remain protected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100