Skip to content

Fix fedify init documentation to match implementation#628

Open
sij411 wants to merge 1 commit intofedify-dev:2.0-maintenancefrom
sij411:fix/init-docs
Open

Fix fedify init documentation to match implementation#628
sij411 wants to merge 1 commit intofedify-dev:2.0-maintenancefrom
sij411:fix/init-docs

Conversation

@sij411
Copy link
Contributor

@sij411 sij411 commented Mar 17, 2026

Summary

  • Remove the obsolete -r/--runtime option section
  • Update -p/--package-manager to list all 5 options and remove Node.js-specific framing
  • Update -w/--web-framework: remove fresh, add next, remove runtime-conditional notes
  • Change -q/--message-queue flag to -m/--message-queue
  • Remove "In-memory"/"in-process" default descriptions from kv-store and message queue
  • Reorder interactive prompt list to match actual prompt flow

Closes #625

Test plan

  • Verify listed options match fedify init --help output
  • Verify options match packages/init/src/const.ts and packages/init/src/command.ts
  • Review rendered docs in VitePress

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 noreply@anthropic.com

The docs/cli.md documentation for `fedify init` was outdated and didn't
match the actual CLI implementation:

 -  Remove the `-r`/`--runtime` option section (no longer exists)
 -  Update `-p`/`--package-manager` to list all 5 options (deno, pnpm,
    bun, yarn, npm) and remove Node.js-specific framing
 -  Update `-w`/`--web-framework` to remove `fresh`, add `next`, and
    remove runtime-conditional notes
 -  Change `-q`/`--message-queue` to `-m`/`--message-queue`
 -  Remove "In-memory"/"in-process" defaults from kv-store and message
    queue sections
 -  Reorder interactive prompt list to match actual prompt flow

Closes fedify-dev#625

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, 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 focuses on enhancing the accuracy and clarity of the fedify init command's documentation. By synchronizing the documentation with the tool's current behavior, it aims to provide users with a more reliable and up-to-date guide for initializing new Fedify projects. The changes streamline option descriptions, remove outdated information, and correct flag names, ultimately improving the user experience for developers setting up their projects.

Highlights

  • Documentation Alignment: The documentation for the fedify init command has been updated to accurately reflect its current implementation, ensuring consistency between the CLI tool and its usage guide.
  • Removed Obsolete Options: The -r/--runtime option section, which is no longer part of the fedify init command, has been removed from the documentation.
  • Updated Package Manager Details: The -p/--package-manager option now correctly lists all five available package managers and removes Node.js-specific framing, presenting a unified list of options.
  • Web Framework Updates: The -w/--web-framework option documentation has been revised to remove the fresh framework, add next (for Next.js), and eliminate runtime-conditional notes for other frameworks.
  • Message Queue Flag Change: The flag for the message queue option has been corrected from -q/--message-queue to -m/--message-queue.
  • Simplified Default Descriptions: Mentions of 'In-memory' or 'in-process' as default options for key-value stores and message queues have been removed from the interactive prompt descriptions.
  • Interactive Prompt Order: The order of items in the interactive prompt list has been reordered to match the actual flow experienced by users.
Changelog
  • docs/cli.md
    • Reordered interactive prompt list items for web framework, package manager, message queue, and key-value store.
    • Removed 'In-memory' default descriptions from key-value store and message queue options in the interactive prompt summary.
    • Removed the entire section for the obsolete -r/--runtime option.
    • Updated the -p/--package-manager section to list all five package managers directly and removed Node.js-specific context.
    • Revised the -w/--web-framework section by removing 'fresh', adding 'next', and eliminating runtime-conditional notes.
    • Changed the message queue option flag from -q/--message-queue to -m/--message-queue.
    • Removed default omission notes for key-value store and message queue options.
Activity
  • The pull request was generated with assistance from Claude Code.
  • Claude Opus 4.6 was a co-author on this pull request.
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.

@issues-auto-labeler issues-auto-labeler bot added component/build Build system and packaging component/cli CLI tools related labels Mar 17, 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

This pull request updates the documentation for the fedify init command to align with recent implementation changes. The changes correctly remove obsolete options, update flags, and adjust descriptions. I've found a couple of minor inconsistencies in the ordering of options within the documentation that could be improved for clarity. Overall, this is a good update to the documentation.

Comment on lines 268 to +272
- `deno`: [Deno]
- `bun`: [Bun]
- `node`: [Node.js]

### `-p`/`--package-manager`: Node.js package manager

If you choose Node.js as the JavaScript runtime, you can specify the package
manager by using the `-p`/`--package-manager` option. The available options
are:

- `npm`: [npm]
- `pnpm`: [pnpm]
- `bun`: [Bun]
- `yarn`: [Yarn]

It's ignored if you choose Deno or Bun as the JavaScript runtime.
- `npm`: [npm]
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The order of package managers in this list is inconsistent with the summary list on line 226. To avoid confusion, both lists should have the same order, and ideally match the order from the codebase (packages/init/src/json/pm.json: deno, bun, npm, yarn, pnpm). Please update both lists for consistency.

Suggested change
- `deno`: [Deno]
- `bun`: [Bun]
- `node`: [Node.js]
### `-p`/`--package-manager`: Node.js package manager
If you choose Node.js as the JavaScript runtime, you can specify the package
manager by using the `-p`/`--package-manager` option. The available options
are:
- `npm`: [npm]
- `pnpm`: [pnpm]
- `bun`: [Bun]
- `yarn`: [Yarn]
It's ignored if you choose Deno or Bun as the JavaScript runtime.
- `npm`: [npm]
- `deno`: [Deno]
- `bun`: [Bun]
- `npm`: [npm]
- `yarn`: [Yarn]
- `pnpm`: [pnpm]

Comment on lines 279 to +283
- `hono`: [Hono]
- `express`: [Express] (unless Deno)
- `nitro`: [Nitro] (unless Deno)
- `nitro`: [Nitro]
- `next`: [Next.js]
- `elysia`: [Elysia]
- `express`: [Express]
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The order of web frameworks in this list is inconsistent with the summary list on line 225 (Hono, Elysia, Express, Nitro, Next.js), which seems to correctly reflect the order in packages/init/src/webframeworks.ts. For consistency, please reorder this list to match.

Suggested change
- `hono`: [Hono]
- `express`: [Express] (unless Deno)
- `nitro`: [Nitro] (unless Deno)
- `nitro`: [Nitro]
- `next`: [Next.js]
- `elysia`: [Elysia]
- `express`: [Express]
- `hono`: [Hono]
- `elysia`: [Elysia]
- `express`: [Express]
- `nitro`: [Nitro]
- `next`: [Next.js]

Comment on lines -227 to -228
- key–value store: In-memory, [Redis], [PostgreSQL], or [Deno KV] (if Deno)
- Message queue: In-memory, [Redis], [PostgreSQL], [AMQP] (e.g., [RabbitMQ]),
Copy link
Member

Choose a reason for hiding this comment

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

@2chanhaeng Do you know why we don't have in-memory options anymore?

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't remember clearly... all the values where value: null like Bare-bones option in the framework have been removed, I think I deleted them assuming they were ignored.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Just to clarify — were the in-memory options intentionally removed, or was it accidental?

Copy link
Contributor

Choose a reason for hiding this comment

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

I didn't intend it.

@codecov
Copy link

codecov bot commented Mar 17, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@dahlia dahlia linked an issue Mar 17, 2026 that may be closed by this pull request
@dahlia dahlia self-assigned this Mar 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component/build Build system and packaging component/cli CLI tools related

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fedify init prompt flow and documented CLI options are out of sync

3 participants