Samaila Bala
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:

Nesting web components in vanilla JavaScript

Nesting web components in vanilla JavaScript

Web components are underrated for the performance and ergonomic benefits they provide in vanilla JS. Learn how to nest them in this post.

Mark Conroy
Dec 5, 2023 ⋅ 10 min read
Using Defer In Angular 17 To Implement Lazy Loading

Using defer in Angular 17 to implement lazy loading

Angular’s new defer feature, introduced in Angular 17, can help us optimize the delivery of our apps to end users.

Lewis Cianci
Dec 4, 2023 ⋅ 10 min read

Using ElectricSQL to build a local-first application

ElectricSQL is a cool piece of software with immense potential. It gives developers the ability to build a true local-first application.

Rahul Padalkar
Dec 1, 2023 ⋅ 11 min read
Using Rust And Leptos To Build Beautiful Declarative User Interfaces

Using Rust and Leptos to build beautiful, declarative UIs

Leptos is an amazing Rust web frontend framework that makes it easier to build scalable, performant apps with beautiful, declarative UIs.

Eze Sunday
Nov 30, 2023 ⋅ 10 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