Provide finer-grained options for approvals.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
Provide finer-grained options for approvals. For example, when approving the command `git log` it's not so useful to have an option to approve all `git` commands as some of those are destructive - but being able to blanket approve all `git log` commands would be helpful.
---
| Field | Value |
| --- | --- |
| App version | 1.1.12 |
| OS | Windows 10.0.26200 |
| Theme | Notionish |
| Path | /chat |
| Tenure | Week 11 |
Contributor guide
Research direction
Start by locating the command approval flow; the issue specifically contrasts blanket approval for all git commands with narrower approval for git log. Define how finer-grained matching should behave for safe and destructive commands, then verify that git log can be approved without approving unrelated git commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100