Other life-changing tip for today: use pr_fetch() to check out the PR of a collaborator locally. 😌

https://usethis.r-lib.org/reference/pull-requests.html

#RStats

Helpers for GitHub pull requests — pull-requests

The pr_* family of functions is designed to make working with GitHub pull requests (PRs) as painless as possible for both contributors and package maintainers. To use the pr_* functions, your project must be a Git repo and have one of these GitHub remote configurations: "ours": You can push to the GitHub remote configured as origin and it's not a fork. "fork": You can push to the GitHub remote configured as origin, it's a fork, and its parent is configured as upstream. origin points to your personal copy and upstream points to the source repo. "Ours" and "fork" are two of several GitHub remote configurations examined in Common remote setups in Happy Git and GitHub for the useR. The Pull Request Helpers article walks through the process of making a pull request with the pr_* functions. The pr_* functions also use your Git/GitHub credentials to carry out various remote operations; see below for more about auth. The pr_* functions also proactively check for agreement re: the default branch in your local repo and the source repo. See git_default_branch() for more.

@maelle I know you linked to them, but the whole `usethis::pr_*()` family is 🥇
pr_init() (cleanly start)
pr_pause() (work on something else in this repo)
pr_resume() (after pr_pausing)
pr_push() (push your work/create the actual remote PR)
pr_finish() (clean up when you're done)
pr_forget() (clean up something you won't finish)
pr_fetch() (get someone else's work for editing or review)
pr_merge_main() (merge main into what you're working on)
@jonthegeek @maelle I still haven't used pr_pause() or pr_resume(), but the others are now my main way of working with branches!
@LeafyEricScott @maelle I've used each once or twice, I think, but it's nice to know I can go fix a different thing if I get deep into the weeds on something.