clearlydefined / clearlydefined/service
Provide Greater Granularity on State of Pull Requests beyond Open/Closed
- Dominant language
- TypeScript
- Stars
- 51
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
As discussed during the Steering Committee meeting today, it was agreed that providing greater granularity of state of pull requests beyond open or closed for a pull request would be goodness for consumers.
Examples of cases where extra information would be beneficial:
a. Pending License Clarification with Project Owner
b. No response to License Clarification with Project Owner
c. Unable to determine applicable licensing due to ...
etc.
Regards,
Sharon
Contributor guide
Research direction
Start by reviewing the current pull request state representation and the consumer-facing service API. Use the examples in this issue to define the additional states, their transitions, and how consumers should observe them before implementation begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100