-
Notifications
You must be signed in to change notification settings - Fork 91
chore: Remove Bucket and replace with Reflag #1264
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
Conversation
✅ Deploy Preview for openfeature ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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 @pavkam, 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 systematically updates the project's codebase to reflect a third-party vendor's recent rebranding. It involves replacing all instances and assets related to the deprecated "Bucket" brand with the new "Reflag" brand, ensuring the application's data and visual elements are current and accurate.
Highlights
- Vendor Rebranding: The pull request updates references from Bucket.co to Reflag.com following their rebranding, ensuring the project aligns with the vendor's new identity.
- Provider Removal: The Bucket provider definition file (src/datasets/providers/bucket.ts) and its associated SVG icon (static/img/bucketco-no-fill.svg) have been completely removed.
- Provider Addition: A new Reflag provider definition file (src/datasets/providers/reflag.ts) and its corresponding SVG icon (static/img/reflag-no-fill.svg) have been added.
- Index File Update: The main providers index file (src/datasets/providers/index.ts) has been modified to remove the old Bucket import/export and include the new Reflag import/export.
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 updates the provider list by replacing Bucket.co with its new brand Reflag.com. The changes are straightforward, involving the removal of the old Bucket provider and its assets, and the addition of the new Reflag provider. The code changes are correct and align with the rebranding. I have one suggestion regarding the new SVG asset to ensure consistency and prevent potential UI issues.
Signed-off-by: Alexandru Ciobanu <alex+git@ciobanu.org>
This PR
Bucket.cohas rebranded intoReflag.com. The SDKs and repos have been renamed. We have deprecated the old SDKs and encourage all users to switch to the Reflag SDKs.Notes
The rebranding announcement: https://www.linkedin.com/posts/reflagcom_reflagcom-activity-7369309036858482689-SA8l?utm_source=share&utm_medium=member_desktop&rcm=ACoAAAEPgdEBHQ4jZ2S1IF0-DdtTnGeGmn5N7hM
Nothing else needs to be done.