microsoft / microsoft/vscode-pull-request-github
Filter comments by reactions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.6k
- Forks
- 795
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 46
Description
GitHub has only the Active and Resolved states for comment threads. This can be painful for complex PRs with large numbers of comments, where it would be more productive to track the status of thread in a finer grained way.
I sometimes use emoji reactions to simulate these states, e.g. using 👀 on the original comment to indicate pending (I'm now working on the change that addresses the thread, I haven't pushed it yet), or 👍 to indicate addressed (I pushed a fix, but original reviewer should check, decide if they agree that the problem is resolved, then hit Resolve on the comment thread).
As part of working with comments "tagged" in these ways, it would be nice to be able to filter the comments list, by whether certain reactions are present on the comments or not.
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 locating the pull-request comment list and its existing Active/Resolved filtering entry points in the repository. Determine how comment reactions are represented, then define filtering for comments with selected reactions; done means the comment list can filter by reaction presence without disrupting existing states.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, typescript
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100