If you’re using Supabase for your project, you might have noticed that Supabase pauses your database after a period of inactivity. This is a common feature in free-tier plans to save resources, but it can be frustrating if you want your database to remain active at all times. Fortunately, you can prevent this by setting up a simple automated “ping” to your Supabase database using GitHub Actions.
In this blog post, I’ll walk you through how to use a GitHub Actions workflow to keep your Supabase database active and prevent it from being paused. I’ll also explain the code and how it works.
<a href="https://medium.com/@jackpritomsoren/how-to-prevent-your-supabase-project-database-from-being-paused-using-github-actions-0257f7fe1edc" target="_blank" rel="noopener nofollow">Read Article</a>

You can share you thought with this squad 

Backend Developer 

Learn how to prevent your Supabase database from being paused due to inactivity by using a GitHub Actions workflow to keep it active. This post details the steps for setting up an automated “ping” to your database, ensuring it remains operational.

How to Prevent Your Supabase Project Database from Being Paused Using GitHub Actions