fix: update codely link #737
Conversation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary of Changes
Hello @anyulled, 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 contains a minor data fix, specifically updating the website link for the 'Codely' sponsor within the application's configuration. This ensures that the displayed link directs users to the correct and current Codely homepage.
Highlights
- Data Correction: The website URL for the 'Codely' sponsor has been updated to its main domain.
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 is currently in preview and 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 to provide feedback.
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. ↩
✅ Deploy Preview for dev-bcn ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Code Review
This pull request updates an outdated, event-specific Codely sponsor link to their main website URL within the primary sponsors data file. This change is appropriate for the current context of the website.
My review includes one comment with medium severity. It suggests checking if the same outdated link exists in historical data files (specifically, the 2023 sponsors data) and considering whether it should also be updated for consistency and user experience on archived pages, or if its preservation is intentional.
| name: "Codely", | ||
| image: "images/sponsors/codely.png", | ||
| website: "https://codely.com/pro/jbcnconf22", | ||
| website: "https://codely.com/", |
There was a problem hiding this comment.
The update to a more general Codely URL (https://codely.com/) is a good improvement, as the previous link (https://codely.com/pro/jbcnconf22) appeared to be event-specific (likely for JBCNConf 2022) and potentially outdated for the current/upcoming event context.
For consistency and to ensure a good user experience on historical pages, please consider if this same outdated link, which also exists in src/2023/Home/components/Sponsors/SponsorsData.ts (line 210), should also be updated to the general URL.
- If past event pages (like the 2023 edition) are intended to have functional and current sponsor links, updating it there would be beneficial.
- If, however, historical data is meant to be an exact snapshot of what was displayed at that time, including potentially outdated links, then leaving it as is might be intentional.
Clarifying the policy for links on historical pages or ensuring consistency would be helpful.
|
No description provided.