Update README.md#263
Conversation
There was a problem hiding this comment.
Summary of Changes
Hello @EmmanuelMalherbe, 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 focuses on a minor but important documentation correction within the README.md file. The primary goal is to ensure the accuracy of a bibliographic citation, improving the overall quality and correctness of the project's documentation.
Highlights
- Documentation Update: The README.md file has been updated to correct a BibTeX entry for the "Better Capturing Interactions between Products in Retail" paper. The entry type was changed from @Article to @inproceedings, and relevant fields were adjusted to reflect this change.
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.
Code Review
This PR updates a BibTeX citation in the README.md file. The new entry contains a duplicated year field and some formatting inconsistencies. I've provided a suggestion to correct the entry to ensure it's valid and consistent with the other citations in the file.
| @inproceedings{Desir2025 | ||
| doi = {}, | ||
| url = {}, | ||
| year = {2025}, | ||
| publisher = {}, | ||
| volume = {}, | ||
| number = {}, | ||
| pages = {}, | ||
| author = {Jules Désir and Vincent Auriau and Martin Možina and Emmanuel Malherbe}, | ||
| title = {Better Capturing Interactions between Products in Retail: Revisited Negative Sampling for Basket Choice Modeling}, | ||
| journal = {} } | ||
| booktitle={Joint European Conference on Machine Learning and Knowledge Discovery in Databases}, | ||
| year={2025}, | ||
| organization={Springer} | ||
| } |
There was a problem hiding this comment.
The updated BibTeX entry has a few issues that could cause problems with citation tools and affect readability:
- Duplicate
yearfield: Theyearis specified on both line 271 and 276. Duplicate fields can cause parsing errors. - Empty
publisherfield: Thepublisherfield on line 272 is empty, whileSpringeris listed underorganization. It's more standard to use thepublisherfield for the publisher's name. - Inconsistent formatting: There's inconsistent spacing around the
=signs (e.g.,booktitle=...vsyear = ...) and the placement of the closing brace.
I've suggested a cleaned-up version that addresses these points for better correctness and consistency with the other entry in this file.
| @inproceedings{Desir2025 | |
| doi = {}, | |
| url = {}, | |
| year = {2025}, | |
| publisher = {}, | |
| volume = {}, | |
| number = {}, | |
| pages = {}, | |
| author = {Jules Désir and Vincent Auriau and Martin Možina and Emmanuel Malherbe}, | |
| title = {Better Capturing Interactions between Products in Retail: Revisited Negative Sampling for Basket Choice Modeling}, | |
| journal = {} } | |
| booktitle={Joint European Conference on Machine Learning and Knowledge Discovery in Databases}, | |
| year={2025}, | |
| organization={Springer} | |
| } | |
| @inproceedings{Desir2025, | |
| doi = {}, | |
| url = {}, | |
| year = {2025}, | |
| author = {Jules Désir and Vincent Auriau and Martin Možina and Emmanuel Malherbe}, | |
| title = {Better Capturing Interactions between Products in Retail: Revisited Negative Sampling for Basket Choice Modeling}, | |
| booktitle = {Joint European Conference on Machine Learning and Knowledge Discovery in Databases}, | |
| publisher = {Springer} } |
Coverage Report for Python 3.10
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Coverage Report for Python 3.11
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Coverage Report for Python 3.12
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Improve the ReadMe file