2020-05-27
1027
#firebase#react
Samaila Bala
19071
May 27, 2020 â‹… 3 min read

Setting up continuous deployment with React, Firebase, and GitHub Actions

Samaila Bala I'm a frontend engineer and technical writer.

Recent posts:

Fix over-caching with dynamic IO caching in Next.js 15

Next.js 15 caching overhaul: Fix overcaching with Dynamic IO and the use cache directive.

David Omotayo
Aug 6, 2025 â‹… 10 min read
LLMs are facing a QA crisis here’s how we could solve it

LLMs are facing a QA crisis: Here’s how we could solve it

LLM QA isn’t just a tooling gap — it’s a fundamental shift in how we think about software reliability.

Rosario De Chiara
Aug 4, 2025 â‹… 7 min read

Windsurf vs. Cursor: When to choose the challenger

Windsurf AI brings agentic coding and terminal control right into your IDE. We compare it to Cursor, explore its features, and build a real frontend project.

Chizaram Ken
Jul 31, 2025 â‹… 9 min read

The CSS if() function: Conditional styling will never be the same

The CSS Working Group has approved the if() function for development, a feature that promises to bring true conditional styling directly to our stylesheets.

Ikeh Akinyemi
Jul 30, 2025 â‹… 12 min read
View all posts

9 Replies to "Setting up continuous deployment with React, Firebase, and GitHub Actions"

  1. Yes you can, all you have to do is modify the flag in `args` of the deploy job to `–only functions,hosting`

  2. Input FIREBASE_TOKEN as the name and the token you copied earlier as the value. After doing that, click Add secret to save the environment variable.

    what is the copied value? is it Firebase-Api-Key or something else. I didn’t get it

  3. Thanks a lot for that! For those people who are a bit confused

    Ensure the branch is “master” or “main”
    repoToken: ‘${{ secrets.GITHUB_TOKEN }}’
    firebaseServiceAccount: ‘${{ secrets.FIREBASE_SERVICE_ACCOUNT_[your project name] }}’

    that’s how it worked for me

Leave a Reply