Skip to content

auth and db migration. getting project back stable.#175

Open
robinroy03 wants to merge 9 commits intomainfrom
feat/auth-and-db-migration
Open

auth and db migration. getting project back stable.#175
robinroy03 wants to merge 9 commits intomainfrom
feat/auth-and-db-migration

Conversation

@robinroy03
Copy link
Member

@robinroy03 robinroy03 commented Feb 22, 2026

once this pr merges:

  1. product will be stable
  2. it will work
  3. it will be scalable

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @robinroy03, 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 primarily focuses on refining the development environment setup and dependency management. It updates the README.md to provide more accurate instructions for starting the backend service and introduces a new configuration in package.json to better manage built dependencies.

Highlights

  • README Update: Corrected the backend startup command in the development instructions and removed an outdated note about the isProduction flag.
  • Dependency Configuration: Added onlyBuiltDependencies to package.json to explicitly list dependencies that should only be built, improving dependency management.
Changelog
  • README.md
    • Updated the uv run command to correctly navigate into the backend directory first.
    • Removed the instruction to flip the isProduction flag in /app/utils/api.ts.
  • package.json
    • Added the onlyBuiltDependencies array with @tailwindcss/oxide and esbuild as entries.
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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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

  1. 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.

@robinroy03 robinroy03 changed the title chore: readme update and package json build confirmation for deps auth and db migration. getting project back stable. Feb 22, 2026
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request updates the development instructions in the README and configures onlyBuiltDependencies in package.json. These changes improve the developer experience by simplifying the backend setup and enhancing security and reliability by explicitly allowing necessary build scripts for dependencies like Tailwind CSS and esbuild. The removal of manual configuration steps in the README is also a welcome cleanup that reduces potential for human error.

@robinroy03
Copy link
Member Author

backend in frontend is cancer. removing it entirely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

demo broken proper ssl for supabase & fix other security issues

1 participant