rfc39 and rfc39-record access for Nixpkgs CI?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 48
- Forks
- 36
- Avg merge
- 2m
- Merged PRs (30d)
- 3
Description
Current permissions seem to be that the infra team has admin access to https://github.com/NixOS/rfc39 and no special access to https://github.com/NixOS/rfc39-record, and the Nixpkgs CI team has no access to either. Given that these repos both pertain to Nixpkgs automation (and rfc39-record will include a GitHub Actions workflow shortly), I humbly suggest giving the Nixpkgs CI team at least triage (and preferably write, so we can edit faulty PR branches or automation if need be) access to at least the rfc39-record repo. (I think giving us rfc39 write access too wouldn't be the worst idea; the repo seemed to be in need of some love.)
Forgot to ping: @NixOS/org
Contributor guide
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
Review the current permissions for NixOS/rfc39 and NixOS/rfc39-record, along with the Nixpkgs CI team's access needs. Confirm the appropriate triage or write level with @NixOS/org, then verify that the requested repository access and workflow-management capability are applied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, github-actions
- Domain
- authorization, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100