Skip to content
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

Be more precise about what initial editor checks can contain #482

Merged
merged 1 commit into from Nov 5, 2021

Conversation

maelle
Copy link
Member

@maelle maelle commented Nov 4, 2021

Cf ropensci/dev_guide#352

I assume the results of pkgcheck are produced prior to the editor filling this.

@emilyriederer
Copy link

I like this a lot! It did inspire one question on this part:

Contributing information: Is the documentation for contribution clear enough e.g. tokens for tests, playgrounds?

Is this something that we should recommend authors have in a specific spot? (e.g. a section in main README? a separate README-DEV?)

@maelle
Copy link
Member Author

maelle commented Nov 5, 2021

Is this something that we should recommend authors have in a specific spot? (e.g. a section in main README? a separate README-DEV?)

Very good point, I clarified https://github.com/ropensci/dev_guide/blob/b65f0ada562fd26ec66335b448337c46f1e3884c/maintenance_collaboration.Rmd#L33 pkgcheck itself has a check looking for that file.

@maelle maelle merged commit c5c93ef into master Nov 5, 2021
@maelle maelle deleted the maelle-patch-1 branch November 5, 2021 11:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants