Skip to content

Add a README for the kits directory - #2976

Merged
IzaakGough merged 5 commits into
kitsfrom
docs-kits-readme
Aug 25, 2026
Merged

Add a README for the kits directory#2976
IzaakGough merged 5 commits into
kitsfrom
docs-kits-readme

Conversation

@IzaakGough

Copy link
Copy Markdown

The kits directory had no README, so there was nothing explaining what a kit is or how the pieces fit together, and the root README did not mention kits at all.

Adds kits/README.md: what a kit is compared with an installed extension, a table of the 13 kits linking to their own READMEs, the firebase.json kit stanza with instance ids and the kits experiment, and a short note on what to check when moving off an installed extension. The root README gets one paragraph linking to it.

Content is drawn from the kit READMEs and package.json files in the tree, not from reading each kit's source. Two things a reviewer may want to weigh in on:

  • The per-kit READMEs all say npm install @firebase/<name>, but every package.json declares @firebase-function-kits/<name>. Since I could not tell which is intended, the new README has no install command. Worth resolving separately.
  • The kit descriptions in the table are the package.json descriptions, lightly trimmed.

Explains what a kit is, lists the kits with links to their READMEs, and
covers the firebase.json kit stanza and instance ids. Links to it from the
root README.
@IzaakGough
IzaakGough marked this pull request as ready for review August 25, 2026 10:33

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

Copy link
Copy Markdown
Contributor

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 introduces documentation for Firebase Function Kits, adding a new README in the kits directory and updating the main README to explain how kits work, how to use them, and how to migrate from extensions. The review feedback focuses on improving the documentation's clarity, grammar, and consistency, including suggestions to use more idiomatic phrasing, standardizing terminology (such as 'deployment schedule', 'ID', and 'behavior'), and fixing placeholder formatting.

Comment thread kits/README.md
Comment thread kits/README.md Outdated
Comment thread kits/README.md Outdated
Comment thread kits/README.md Outdated
IzaakGough and others added 4 commits August 25, 2026 11:37
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>

@cabljac cabljac left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

lgtm

@IzaakGough
IzaakGough merged commit e1ed0fc into kits Aug 25, 2026
9 checks passed
@IzaakGough
IzaakGough deleted the docs-kits-readme branch August 25, 2026 10:49
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.

2 participants