-
- Notifications
You must be signed in to change notification settings - Fork 40
Prepare CRAN submission #1164
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
Prepare CRAN submission #1164
Conversation
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.
Summary of Changes
Hello @strengejacke, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request prepares the 'parameters' R package for a new CRAN submission. The changes primarily involve updating the package version, aligning dependency requirements with recent releases of other 'easystats' packages, and adjusting the 'Remotes' field to meet CRAN submission guidelines.
Highlights
- Version Update: The package version has been incremented from 0.28.0.16 to 0.28.1, indicating a new release.
- Dependency Alignment: Minimum version requirements for several key imported and suggested packages (bayestestR, insight, effectsize, marginaleffects, glmmTMB) have been updated or removed to align with their latest stable releases or to relax strict version checks in tests.
- CRAN Submission Preparation: The 'Remotes' field in the DESCRIPTION file has been significantly streamlined, now only pointing to a specific commit of 'bayestestR' on GitHub. This is a step towards removing the 'Remotes' field entirely once 'bayestestR' is available on CRAN, which is a requirement for CRAN submissions.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review | Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary | Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help | Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
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.
Code Review
This pull request prepares the package for a CRAN submission by updating the version number and dependency requirements across various files, including DESCRIPTION
, R source files, and tests. The changes are generally consistent and correct. However, I've identified a small typo in one of the test files that should be addressed.
Remove reference to bayestestR issue #736 from DESCRIPTION.
easystats/bayestestR#736