Skip to content

Commit

Permalink
Link to the pr_*() functions
Browse files Browse the repository at this point in the history
  • Loading branch information
jennybc committed Dec 21, 2021
1 parent 37e5be0 commit 7ddbe31
Showing 1 changed file with 10 additions and 2 deletions.
12 changes: 10 additions & 2 deletions workflows-explore-extend-pull-request.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,12 @@ Scenario: you maintain an R package on GitHub with pull requests (PRs) from exte

How do you checkout and possibly extend an external PR?

## Update from the future

The lessons learned here eventually lead to the `pr_*()` family of functions in usethis.
`pr_fetch()` and `pr_push()` are now my workhorses for exploring and extending PRs.
You can read more about usethis's functions to help with pull requests in their very own article: [Pull request helpers](https://usethis.r-lib.org/articles/pr-functions.html).

## Terminology

Vocabulary I use throughout.
Expand Down Expand Up @@ -77,9 +83,11 @@ This set of instructions suggests that you clone the fork, checkout the branch f

My main takeaway: maintainer can push to the branch of a fork associated with a PR.

## My under-development workflow
## A workflow I once used

*work in progress*
*The lessons learned here eventually lead to the `pr_*()` family of functions in usethis.
`pr_fetch()` and `pr_push()` are now my workhorses for exploring and extending PRs.
You can read more about usethis's functions to help with pull requests in their very own article: [Pull request helpers](https://usethis.r-lib.org/articles/pr-functions.html).*

This combines ideas from the three above approaches, but with a few tweaks. I am sketching this up in R code, with the hope of putting this into a function and package at some point. This is a revision of an earlier approach, based on feedback from Jim Hester.

Expand Down

0 comments on commit 7ddbe31

Please sign in to comment.