-
Notifications
You must be signed in to change notification settings - Fork 287
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should use_github_links()
really be on the release checklist?
#1805
Comments
I recently had an experience when spring cleaning which made me add this commit:
What was the full before and after for vctrs? I.e. if vctrs only listed the pkgdown site, I assume you would want to add the GitHub site. So maybe there's also something here about appending? Related: I think it's also possible that we should have |
Yea so unlike dplyr:
the vctrs URLs only include the pkgdown site
I'm not opposed to adding the github one too |
Also for context, here's why it got added: #1704 |
It's definitely our de facto standard to have both the pkgdown site and the GitHub site and I really hope we're not talking about changing that. |
Yea it sounds like maybe the detection of the github link is working, but it should be appending to the list of existing urls rather than overwriting them entirely? |
I think up 'til now we've basically accepted that if this function does something to your |
I think:
If this sounds right I'll do a PR so that |
Yes @ateucher sounds like a good plan. |
It comes with
usethis::use_release_issue()
It tries to change
URL: https://vctrs.r-lib.org/
toURL: https://github.com/r-lib/vctrs
, which is not what we wanted.@hadley said this is likely a more community focused function, so we probably don't need it in our release checklist?
The text was updated successfully, but these errors were encountered: