chainguard-dev / chainguard-dev/ghaudit
Have each command document required permissions
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 12
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
Each should give a sample Octo STS permissions block.
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 listing the commands exposed by the CLI and checking their existing documentation. For each command, document the required permissions with a sample Octo STS permissions block; the work is done when every command has this information.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, go
- Domain
- cli, documentation, security
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100