-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
[PRE REVIEW]: lintr: Static Code Analysis for R #7171
Comments
Hello human, I'm @editorialbot, a robot that can help you with some common editorial tasks. For a list of things I can do to help you, just type:
For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:
|
|
Software report:
Commit count by author:
|
Paper file info: 📄 Wordcount for ✅ The paper includes a |
License info: 🟡 License found: |
|
@editorialbot generate pdf |
Five most similar historical JOSS papers: quanteda: An R package for the quantitative analysis of textual data TextDescriptives: A Python package for calculating a large variety of metrics from text Welcome to the Tidyverse glottospace: R package for language mapping and geospatial analysis of linguistic and cultural data LinRegOutliers: A Julia package for detecting outliers in linear regression |
Never mind, I now see you have already handled this, appreciate you being on top of it and thanks! |
thanks for flagging @jimhester! it was (partially) fixed already: r-lib/lintr#2651 this comment is the updated paper: |
@crvernon you mind If I assign myself as editor on this one ? |
@editorialbot assign @lrnv as editor Thanks @lrnv! |
Assigned! @lrnv is now the editor |
@jimhester Happy to be your editor for this meaningful package in the R realm. To start off, would you be able to recommend a few potential reviewers for this ? For example if you have people that you know will give you interesting input on the submission, that might fit. |
https://reviewers.joss.theoj.org/reviewers/720, https://reviewers.joss.theoj.org/reviewers/1337 are a couple I noticed from a brief look. Josiah and I overlapped at RStudio a bit as a potential COI, but we never worked on any projects together and have both been gone from RStudio for > 2.5 years. @MichaelChirico or @IndrajeetPatil do you have any other reviewer suggestions? |
Also looked briefly; maybe https://reviewers.joss.theoj.org/reviewers/2436 who has worked on the R Dev Guide & other R forwards initiatives |
Okay then, @njtierney, @JosiahParry, @SaranjeetKaur would any of you be willing to review |
I would love to! Thanks! |
Thanks for thinking of me :) Yes, I would be happy to submit a review. |
@editorialbot add @JosiahParry as reviewer |
@JosiahParry added to the reviewers list! |
@editorialbot add @SaranjeetKaur as reviewer |
@SaranjeetKaur added to the reviewers list! |
@editorialbot start review |
OK, I've started the review over in #7240. |
Submitting author: @jimhester (James Hester)
Repository: https://github.com/r-lib/lintr
Branch with paper.md (empty if default branch):
Version: v3.1.2
Editor: @lrnv
Reviewers: @JosiahParry, @SaranjeetKaur
Managing EiC: Chris Vernon
Status
Status badge code:
Author instructions
Thanks for submitting your paper to JOSS @jimhester. Currently, there isn't a JOSS editor assigned to your paper.
@jimhester if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.
Editor instructions
The JOSS submission bot @editorialbot is here to help you find and assign reviewers and start the main review. To find out what @editorialbot can do for you type:
The text was updated successfully, but these errors were encountered: