chore: drop all stale migrations

[fulleni]

Status

READY

Description

This pull request focuses on codebase maintenance by removing a series of database migration scripts that are no longer necessary. These migrations, having already been applied to the database, are now considered stale. Their removal simplifies the project's migration directory and ensures that only relevant, active migration logic is retained, contributing to a cleaner and more manageable codebase.

Type of Change

• ✨ New feature (non-breaking change which adds functionality)
• 🛠️ Bug fix (non-breaking change which fixes an issue)
• ❌ Breaking change (fix or feature that would cause existing functionality to change)
• 🧹 Code refactor
• ✅ Build configuration change
• 📝 Documentation
• 🗑️ Chore

[gemini-code-assist]

Summary of Changes

Hello @fulleni, I'm Gemini Code Assist¹! 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 codebase maintenance by removing a series of database migration scripts that are no longer necessary. These migrations, having already been applied to the database, are now considered stale. Their removal simplifies the project's migration directory and ensures that only relevant, active migration logic is retained, contributing to a cleaner and more manageable codebase.

Highlights

• Migration Cleanup: Removed eight stale database migration files, streamlining the project's migration management.
• Migration Registration Update: The allMigrations list in all_migrations.dart has been emptied, reflecting the removal of the associated migration scripts.

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

[gemini-code-assist]

Code Review

This pull request removes all existing database migrations. While this can be a valid cleanup task (often called 'squashing migrations'), it appears to have been done without providing an alternative way to set up a new database schema. As detailed in my comment, this is a critical issue that could prevent new developers or new deployments from successfully initializing the application. Please address this concern.