Remove some git /github related defunct functions

[olivroy]

As they clutter the autocompletion?

I did gh code search and the functions don't seem widely used as people have made the switch over the last 3.5 years. I opened a few PRs and issues as FYI to avoid ugly messages in advance.

I also added a few redirection rules in pkgdown config to be on the safe side!

https://github.com/search?q=saved%3A%22usethis+deprecate%22+&type=code&saved_searches=%5B%7B%22name%22%3A%22usethis+deprecate%22%2C%22query%22%3A%22browse_github_pat++NOT+is%3Aarchived+NOT+is%3Afork%22%7D%5D&expanded_query=browse_github_pat++NOT+is%3Aarchived+NOT+is%3Afork+

[jennybc]

I opened a few PRs and issues as FYI to avoid ugly messages in advance.

Can you mention this PR in those PRs and issues, so they get linked here and I can see exactly what you're talking about?

[olivroy]

• mention pr_merge_main() instead of pr_pull_upstream() annakrystalli/rrresearchACCE20#14
• Avoid mentioning browse_github_pat() as it is deprecated annakrystalli/talks#9
• Avoid mentioning usethis::browse_github_pat() and usethis::github_token() jimbrig/property_allocation_demo#4
• Avoid mentioning browse_github_pat() Edouard-Legoupil/kobocruncher#11
• Avoid mentioning browse_github_pat() KWB-R/kwb.pkgbuild#92
• Refer to create_github_token() instead of browse_github_pat() tlverse/tlverse-handbook#35
• usethis deprecated features tlverse/tlverse#4
• Avoid mentioning deprecated usethis function in docs ropensci/circle#42
• Remove mention of browse_github_pat() SticsRPacks/documentation#2
• Avoid mentioning deprecated function matt-dray/rostrum-blog-2#41
• Avoid browse_github_pat() MazamaScience/AirSensorDataViewer#60
• Mention create_github_token() instead of browse_github_pat() rstudio/shinycoreci#266
• Add link to DESCRIPTION + avoid mentioning usethis::browse_github_pat() vnijs/gitgadget#3

Mostly mentioned the functions in older docs

[jennybc]

This is not in scope for the next release, as it looks pretty fiddly, for a modest payoff.

In order to sort this out, it would be helpful to make it clear which of the PRs are to packages on CRAN/Bioconductor (which we cannot break, at least not without sufficient warning) vs. other stuff (blog posts, talks, etc., where the issue/PR is just courtesy).

[olivroy]

The PRs are all courtesy. No breakage will happen. As you can see, the PRs and issues have mostly been ignored (namely becsuse they were on old unmaintained projects) The only reason why I added redirects in _pkgdown.yml was as courtesy, but they are not required.

[jennybc]

Thanks!

[jennybc]

The PRs are all courtesy. No breakage will happen.

It turns out github_token() is used by a package on CRAN:

https://github.com/ropensci/circle/blob/f8a4fbf6f792c3f462df1749b90cca9c31214e3a/R/use-circle-deploy.R#L39

[olivroy]

I didn't catch this occurrence in my search.. but use_circle_deploy() is broken (and has been for a while now)

[jennybc]

I don't think this matters much in practice, because I suspect that the use of this package (circle) is minimal / non-existent, given how much folks have pivoted from Circle CI to GitHub Actions. In any case, usethis made it onto CRAN even with this mild breakage, since github_token() has been hard deprecated since December 2020. If this was actually bothering folks, it would have been updated by now.