Come up with a process to champion a PR on a Typelevel project
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- developer-experience
Research direction
Start by reviewing the discussion in issue #207 and the three proposed ideas about researching, explaining, and pairing on a PR. Define and agree on a championing process for Typelevel PRs, including what the champion does and what completion of the process means.
Written by the indexing model from the issue text.
Description
We were discussing the idea of championing a PR that should be approved.
Some ideas
- That person would research, and ensure running
- Describe why it should be approved
- Perhaps pair with someone as discussed with @Koroeskohr
- Dominant language
- No language data
- Stars
- 11
- Forks
- 4
- Avg merge
- 1h 49m
- Merged PRs (30d)
- 2
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.
More from typelevel/tsc
-
Migrating: GatOS Openprojects
Difficulty 1/5 Under an hour Newbie friendliness 72/100
-
affiliation
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
use-agent-os/agent-os#3314 ·
-
documentation low-priority templates
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
jesseray718/openroot#87 ·
-
factory-active factory-automatic task-bug-reproduction-cannot-reproduce task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
in-progress proposal
Difficulty 1/5 Under an hour Newbie friendliness 88/100
uibcdf/molsyssuite#36 ·