evaluate to use a PR review process
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- developer-experience
Research direction
Review the linked finalsize pull-request example and compare its review workflow with the tutorials project's package-development process. Decide whether PR reviews should be used as checkpoints before making a PR, and document the recommendation and criteria for accepting or rejecting contributor edits.
Written by the indexing model from the issue text.
Description
RSEs use PR reviews as checkpoints in the closing of a package development process. Here is an example for one package. It facilitates direct edits and an accept/reject of them, with a review request to contributors, and other features. I do not have a reference for this but we can evaluate this for the moment of deciding to make the PR.
- Dominant language
- R
- Stars
- 3
- Forks
- 7
- PR merge metrics
- No merged PRs in 30d
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 epiverse-trace/tutorials
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
epiverse-trace/tutorials#242 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
epiverse-trace/tutorials#241 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
epiverse-trace/tutorials#240 ·
-
priority
epiverse-trace/tutorials#234 · 1 assignee ·
-
epiverse-trace/tutorials#233 · 1 assignee ·
All issues in epiverse-trace/tutorials
Similar issues
-
documentation pkg infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
epiverse-trace/epiparameter#511 ·
-
function:write_dwc
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Urgent request: Due to vulnerabilities move to API version 12.6.1 (12.6.2 eventually) or 13.1.1 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
jbkunst/highcharter#849 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
r-lib/pkgdepends#485 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100