Skip to content

Conversation

@hadley
Copy link
Member

@hadley hadley commented Jan 18, 2023

Fixes #1665

Copy link
Member

@jennybc jennybc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This the only deleted sentence that I'm a bit sad to see go:

#' ... `pr_fetch()` puts a
#' maintainer in a position where they can push changes into an internal or
#' external PR via `pr_push()`.

@hadley
Copy link
Member Author

hadley commented Jan 19, 2023

I didn't go with that exact wording, but hopefully communicated the same message.

#' and pulling any changes from its upstream tracking branch, if it has one. If
#' called with no arguments, up to 9 local branches are offered for interactive
#' selection, with a preference for branches connected to PRs and for branches
#' with recent activity.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we mention that pr_resume() can be useful if you've used pr_pause() but have not yet called pr_push()? But otherwise we generally use pr_fetch() because you can reference by PR number and that is typically a little easier?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added some text to pr_pause() to hopefully help here.

@hadley hadley merged commit 083afee into main Jan 19, 2023
@hadley hadley deleted the fetch-vs-resume-docs branch January 19, 2023 16:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Could pr_resume() also work off PR numbers?

4 participants