A way to manage access around who can edit contents of `.github/workflows/`
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
Enhancement: Provide role separation around who can edit contents of .github/workflows/
Reasoning: In an organization setting you have a lot of people who have write access to repositories. Add github actions workflows and secrets manager (think org level secret manager when it is released) and every person with write access could change a workflow file or create a new workflow file to print out the contents of a secret. Being able to limit the people who can edit workflows would be a huge plus in the security front.
@ds0440 @josephshanahan-cfa
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 57-comment discussion and the repository's .github/workflows context. Define how role separation for editing workflow files would work with organization-level secrets, and consider the work complete when the access model and its boundaries are specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- authorization, ci-cd, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100