Add commands to list issues and PRs
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
The issue names no files, tests, or entry points. Start by mapping the existing command structure and GitHub query integration, then define the command boundaries for review-needed, merged or closed items, and user-specific assignments and status. Done should mean the agreed commands return each requested result reliably.
Written by the indexing model from the issue text.
Description
Might want to do several commands here:
- what PRs need review and are unassigned
- what PRs were merged yesterday, what issues were closed
And specific to a user:
- what PRs did that user merge yesterday
- as a reviewer: what PRs are they assigned to, what is their status
- as an author: what PRs are open and what is their status, what issues are they assigned to
- Dominant language
- Python
- Stars
- 16
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from mitodl/release-script
-
Dependency DashboardOpen
Difficulty 5/5 Over a week Newbie friendliness 15/100
mitodl/release-script#381 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
mitodl/release-script#371 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
mitodl/release-script#368 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
mitodl/release-script#367 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
mitodl/release-script#366 ·
All issues in mitodl/release-script
Similar issues
-
feature:LinkChecker
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
digitalfabrik/integreat-cms#4594 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
EleutherAI/lm-evaluation-harness#4319 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
json_params_matcher fails on falsy top-level JSON primitives (0, False, "")Possibly taken @mayureshsonawane17 claimed this today. OpenWaiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 5 days