Jared Beck

> @jaredbeck: git push without arguments should push changes back to the PR, even if the PR comes from a fork, and even if there is no git remote for...

> Could this be better documented? It'd be nice if `gh pr checkout` printed something like: "This new branch's `config` will track the fork at __. You can push to...

@nwu63 What does the following command print? ``` git config --get-regexp "^branch\\.$(git branch --show-current)\\." ```

Per the ruby documentation: > The instance-method versions are made private. > http://ruby-doc.org/core-2.2.2/Module.html#method-i-module_function

After 14 months, this issue has not attracted the attention of any maintainers, so I'm closing it. Thanks to everyone who provided feedback. I think if someone were to summarize...

> Yep, [making them private] was the point. 😄 Cool. Yeah, are we ready to turn this discussion into a PR, and add an explanation to [this rule](https://github.com/rubocop-hq/ruby-style-guide/#module-function)?

Also, weirdly, it looks like 6.15.0 (which, like 17 is in the changelog) was never published either?

## Workaround Use `Byebug.start_server` and `byebug -R`. You don't need `pry-remote`, `pry`, `pry-nav`, or `pry-remote`. You don't need any pry-stuff. All you need is `byebug`. It's not well documented, but...

This is the last blocker in my app preventing our upgrade to Faraday 2. `elasticsearch-persistence -> elasticsearch 7 -> elasticsearch-transport 7 -> faraday 1` Looking forward to a release, thanks...

Please rebase and push to trigger new test run