-
Notifications
You must be signed in to change notification settings - Fork 13
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
Data Documentation for load_espn_qbr #74
Conversation
Awesome! You can check locally to see if the pkgdown will build by running |
Can you also run |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See typo note + please redocument with devtools::document()
(usually twice), then commit/push those here and the checks should pass
thanks for getting back! might be a dumb question, but where should I run devtools::document()? |
Just in your console, it'll operate over the whole package |
Head branch was pushed to by a user without write access
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Hey guys,
I thought I'd try and give back to the nflreadr because of how helpful it is, so I started to work on one of the "good first issues" that were listed. To start, I created a data dictionary for the "load_espn_qbr" package which is what this pull request is for. Everything seems to work fine on my end in R (if I load in my forked github using devtools), but I'm not sure on how to test if my updates are also shown in the pkgdown website.
Please let me know if I did anything wrong, and any feedback would be much appreciated. Thanks for all you do for the community!