-
Notifications
You must be signed in to change notification settings - Fork 143
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
Pull Request: (sindresorhus/awesome) or (qinwf/awesome-R) #9
Comments
My vote would be
|
Ok good deal! @ucg8j This might make it clearer.
So we could do one of the first options and one of the second options. |
Cool! I've just submitted a pull request on awesome-R. There's quite a lot of open PRs so that might take a while. It looks like @sdhutchins PR has been accepted. Ah, I think it just clicked as to what you meant. Add on this awesome list, a link to the awesome-R page? |
Not exactly. Sorry I can see how that was confusing. What I meant by 'Merge with Awesome-R' was to basically add an r-Shiny section to their list. So we copy and paste all of our README.md into their README.md. But I don't think that will be useful after all. @ucg8j |
So @ucg8j's PR went through on Awesome-R! |
Can we go ahead and close this out? @grabear |
Not yet. The other PR is still open. I'll look at the guidelines for the main awesome list to make sure we comply. |
Didn't even realize it was still open. Hmmm. |
Where should we put the awesome-rshiny list? @sdhutchins @daattali @dpastoor @ramnathv @ucg8j
The text was updated successfully, but these errors were encountered: