Proposal : Add block-on-denounce opt-in flag to manage actions
Nobody has claimed this yet.
- Dominant language
- Nushell
- Stars
- 5.1k
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
I would like to work on the issue #86 created by @mitchellh. From my understanding of the repo structure, the change belongs in the vouch/github.nu , where a successful denounce would call GitHub's block API to block the target user. Conversely, a successful vouch/unvouch action will call the unblock API. I am thinking about adding a opt-in flag to control if blocking happens and expose it in manage-by-issue/action.yml and manage-by-discussion/action.yml files. If this sounds good or requires any change, let me know.
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
Start with issue #86 and inspect vouch/github.nu to understand the existing denounce, vouch, and unvouch flows and their GitHub API calls. Then review manage-by-issue/action.yml and manage-by-discussion/action.yml for the opt-in configuration surface. Done means the flag consistently controls the described block and unblock behavior in both actions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, github-actions
- Domain
- api, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100