feat!: reconstruct prisma commands for litestream

[exKAZUu]

Close #

Self Check

• I've confirmed All checks have passed on this page.
  • PR title follows Angular's commit message format.
  • PR title doesn't have WIP:.
  • The test command (e.g., yarn test) passed.
  • The lint command (e.g., yarn lint) passed.
  • You may leave this box unchecked due to long workflows.
• I've reviewed my changes on the GitHub diff view.
• I've written the steps to test my changes.
• I've added screenshots (if the UI changed).
  • You may leave this box unchecked if you didn't modify the UI.

[gemini-code-assist]

Summary of Changes

Hello @exKAZUu, 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 refactors the Prisma command-line interface by introducing a dedicated command for cleaning up Litestream-related files and renaming an existing command to better reflect its singular purpose of setting up the database for Litestream. These changes enhance the organization and clarity of Litestream management operations within the Prisma command suite, making the command structure more modular and easier to understand.

Highlights

• New Command for Litestream Cleanup: A new prisma cleanup-litestream command has been introduced to explicitly handle the removal of temporary Litestream files, improving clarity and separation of concerns.
• Renamed and Refocused Command: The prisma litestream command has been renamed to prisma setup-db-for-litestream. Its responsibility is now solely focused on setting up the database for Litestream replication, with the cleanup logic moved to the new cleanup-litestream command.
• Command Reordering: The registration order of Litestream-related commands within the prisma command builder has been adjusted for a more logical and intuitive flow.

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

このプルリクエストは、Litestream関連のPrismaコマンドを再構築するもので、cleanup-litestreamコマンドの追加やlitestreamコマンドのsetup-db-for-litestreamへのリネームなど、主にリファクタリングと命名の変更が行われています。全体的に良い変更ですが、1点、リネームされたコマンドのログメッセージが古い名前のままになっている箇所がありましたので、修正を提案します。

I am having trouble creating individual review comments. Click here to see my feedback.

packages/wb/src/commands/prisma.ts (110)

コマンドが litestream から setup-db-for-litestream にリネームされましたが、ここのログメッセージで使われているコマンド名が古いままです。ユーザーに表示されるメッセージなので、実際のコマンド名と一致させるべきです。
prepareForRunningCommand に渡す文字列を 'prisma setup-db-for-litestream' に更新してください。

    for (const project of prepareForRunningCommand('prisma setup-db-for-litestream', allProjects)) {

[Copilot]

Pull request overview

This PR refactors the Litestream-related Prisma commands by splitting the monolithic litestream method into two separate, more focused methods: cleanUpLitestream (for cleaning up temporary Litestream artifacts) and setUpLitestream (for configuring the database for Litestream). The corresponding CLI commands are renamed to cleanup-litestream and setup-db-for-litestream for better clarity.

Key changes:

• Split litestream() method into cleanUpLitestream() and setUpLitestream() in prismaScripts.ts
• Renamed CLI command from litestream to setup-db-for-litestream and added new cleanup-litestream command
• Reordered command definitions for better organization (alphabetical or logical grouping)

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
packages/wb/src/scripts/prismaScripts.ts	Adds cleanUpLitestream() method and renames litestream() to setUpLitestream(), separating cleanup logic from DB setup logic
packages/wb/src/commands/prisma.ts	Adds cleanUpLitestreamCommand, renames litestreamCommand to setUpDBForLitestreamCommand, and reorders command definitions

Comments suppressed due to low confidence (1)

packages/wb/src/commands/prisma.ts:110

• The command string passed to prepareForRunningCommand should be 'prisma setup-db-for-litestream' to match the renamed command, not 'prisma litestream'. This inconsistency could cause logging or tracking issues. All other commands in this file follow the pattern of using 'prisma ' where command-name matches the command field.

    const unknownOptions = extractUnknownOptions(argv);

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.