List user's open cpython PRs, add "get info from PR" button
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github, python
- Domain
- developer-experience
Research direction
Start by reviewing the existing workflow for clicking a PR to get information, then separate the request into the three proposed workflows: listing open CPython PRs, fetching PR information, and updating an existing blurb. Confirm the scope with the maintainers before defining done, since the issue is explicitly high-level and asks whether all requested work belongs in blurb-it.
Written by the indexing model from the issue text.
Description
At PyConUS in the sprints and hoping to make some workflow improvements based on new developers using blurb. Can split into multiple issues, but high level:
- List the most recent open CPython PRs by the user (limited to a smallish number)
- Add a "fetch" button so given the github PR number can get information on it (github issue, if there is an existing blurb). Limit the max "fetch file" size. (This same infra used for "click on PR -> get info)
- Be able to update an existing blurb in the PR (simple edits without having to figure out git workflow)
Happy to split into multiple smaller issues/prs. If any of these are outside scope of the blurb-it app let me know
- Dominant language
- Python
- Stars
- 33
- Forks
- 22
- Avg merge
- 23m
- Merged PRs (30d)
- 2
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.
More from python/blurb_it
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
syfoud/Simulated_Scepter#172 ·
-
A cancelled tests run makes the coverage comment workflow fail and reports it as a red check on main Openarea: ci bug perceived difficulty: 3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Nitjsefnie-Harness-Commons/daedalus#921 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
EleutherAI/lm-evaluation-harness#4207 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-connect#1057 ·