From a6e566c41fe217184e50088c6dffd75ec4ecc3ad Mon Sep 17 00:00:00 2001
From: Copple <10214025+kiwicopple@users.noreply.github.com>
Date: Thu, 3 Aug 2023 10:28:40 +0200
Subject: [PATCH] Adds a warning

---
 docs/backups.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/docs/backups.md b/docs/backups.md
index 108b7c6..95d5fc9 100644
--- a/docs/backups.md
+++ b/docs/backups.md
@@ -1,7 +1,11 @@
 # Backup your database
 
 You can use the Supabase CLI to backup your Postgres database. The steps involve running a series of commands to dump roles, schema, and data separately.
-Inside your repository, create a new file inside the `.github/workflows` folder called `backup.yml`. Copy the following snippet inside the file, and the action will run whenever a new PR is created:
+Inside your repository, create a new file inside the `.github/workflows` folder called `backup.yml`. Copy the following snippet inside the file, and the action will run whenever a new PR is created.
+
+!!! note
+
+    Never backup your data to a public repository. 
 
 ## Backup action
 
@@ -33,6 +37,10 @@ The workflow runs on the latest Ubuntu runner and requires write permissions to
 After the backup is complete, it auto-commits the changes to the repository using the `git-auto-commit-action`. This ensures that the latest backup is always available in your repository. The commit message for these automated commits is "Supabase backup".
 This workflow provides an automated solution for maintaining regular backups of your Supabase database. It helps keep your data safe and enables easy restoration in case of any accidental data loss or corruption.
 
+!!! note
+
+    Never backup your data to a public repository. 
+
 ```yaml
 name: Supa-backup