The GitHub community is capable of incredible things! GitHub Actions is just one of the amazing tools made available for developers. Actions is here to help you automate your workflows, deploy to any cloud, build containers, and so much more!

Over the next few weeks, we’re sharing the stories from some of the earliest GitHub Actions adopters. Learn about their projects, challenges, and lessons learned.

This week’s GitHub Actions Hero

Today, we speak with Jeremy Shore (@w9jds_), the creator of GitHub Action for Firebase, to find out the story behind their GitHub Action.  _

Jeremy started his software career in the gaming industry. Like many developers, he simply loved what he was doing and used that passion to find a the job he enjoyed:

I’m a software engineer at PlayStation. I created a ton of tools in my free time for people that play Eve Online, as well as for Google Developer Groups, and personal use. I just really enjoy it and do it for fun.

Firebase Action

The GitHub Action “Firebase” was built to help Jeremy with one of the problems he was facing. Jeremy hosts three firebase sites and over 25 other firebase cloud functions. Firebase gives you the power to simply push, build, and deploy to the repo without the need to host anything from your own laptop environment. Originally, the Action was created in order to check what functions had been updated and only deploy a function if it needed changing. During the GitHub Hackathon, Jeremy built on the Firebase Action:

I wanted to handle pushing updates to firebase/firestore after a build has completed to trigger cloud functions, pub-subs, and/or notifications to users that a new build has been deployed

#actions #developer #firebase #github actions #shore