torresalmonte

const admin = require('firebase-admin');

// expects the environment variable GOOGLE_APPLICATION_CREDENTIALS
const serviceAccount = require(process.env.GOOGLE_APPLICATION_CREDENTIALS);
const credential = admin.credential.cert(serviceAccount);

const PROJECT_ID = '<FIREBASE_PROJECT_ID>';

const app = admin.initializeApp({
    credential: credential

torresalmonte

const admin = require('firebase-admin');
const {sleep} = require('sleep');

// asumes the existance of the GOOGLE_APPLICATION_CREDENCIAL env variable
const firebaseApp = admin.initializeApp();

async function getRulesets(projectId, firebaseApp, pageToken) {

    pageToken = pageToken || '';

mbleigh

Fetch All Files from Firebase Hosting

This script fetches all of the files from the currently deployed version of a Firebase Hosting site. You must be signed in via the Firebase CLI and have "Site Viewer" permission on the site in question to be able to properly run the script.

Running via NPX

npx https://gist.github.com/mbleigh/9c8680cf319ace2f506f57380da66e7d <site_name>

jaromero

Commit Message Guidelines

These guidelines are meant to be a simple, effective way to quickly discern the type of contribution in our projects, as well as an attempt to enforce limiting commits to a single topic and avoid unwieldy commits

It's based on Angular's contribution guidelines, and this document about commit messages in general. I suggest that you give them a read, too.

The general idea

A commit message consists of, at the very least, the summary. It may also include a body, separated from the summary by a blank line.