action-hosting-deploy VS husky

Could they not have their own FB to develop against? Does every dev need to use just yours? If that is the case, then you'd need to use https://support.google.com/firebase/answer/7000272?hl=en also, it looks to be possible to include Firebase in your GitHub for them to pull from https://firebase.google.com/docs/hosting/github-integration

Github Actions is the way to go for this: https://firebase.google.com/docs/hosting/github-integration

Whenever a Pull Request is created we need to be able to quickly checkout the changes. Reading code diff is great, but sometimes you just need to tinker with the new version, test it on mobile, different browsers and OS. Cloud services are perfect for this case, they allow you to deploy the code temporarily and access it with a link from any device. We chose Firebase to host it for us and a Github action posts a link to the deployment as a comment in the Pull Request. It works like a charm and speeds up code reviews a lot. Read this article to set it up on your repository!

Lambdas and firebase on the GCP stack for CRUD apps.

One nice thing about firebase -> each PR deploys to its own preview channel[1].

Downside: Very JS heavy. I write lambdas in python though.

[1] https://firebase.google.com/docs/hosting/github-integration

Google Firebase has a pretty straightforward guide to setting up auto-deploy from Github, which you can take a look at here: https://firebase.google.com/docs/hosting/github-integration

What is the easiest way for setting up CI/CD from GH for Firebase functions? Maybe something like this for hosting, but only for functions?

Note: you can find more info about the used steps actions here actions/checkout@v2 and here FirebaseExtended/action-hosting-deploy@v0

In this post, I will primarily discuss client-side hooks. I'll delve into three specific hooks: pre-commit, commit-msg, and pre-push. The central tool discussed will be Husky, which simplifies the configuration of Git Hooks, making it more straightforward.

Reading Biome doc I also switched from husky to lefthook.

Dive deeper into the world of Husky with the official documentation. Explore the capabilities of Standard Version through its comprehensive documentation. Unravel the mysteries of semantic-release with its detailed documentation. Discover the versatility of bumpp with its comprehensive documentation.

Let’s walk through the steps for a one-time setup to configure husky pre-commit and pre-push hooks, ESLint with code styles conventions, prettier code formatter, and lint-staged. Husky automatically runs a script on each commit or push. This is useful for linting files to enforce code styles that keeps the entire code base following conventions.

We were already using lint-staged and have a pre-commit hook in place using Husky in our project for linter and prettier. So it made sense to add a check here.

Now, let's talk about Husky. It's a wonderful tool that enables you to run scripts on any Git hooks. We'll add a pre-commit hook to run ESLint and Stylelint checks before committing. This ensures that we don't commit code with errors.