Supabase
Branching - Early access | Feedback discussion #18937
Replies: 219 comments 549 replies
-
What is Supabase Branching? |
Beta Was this translation helpful? Give feedback.
-
|
In the most concise sense, you can use branching to safely and easily experiment with changes to your Supabase projects. |
Beta Was this translation helpful? Give feedback.
-
|
Is branching expected to be available only from |
Beta Was this translation helpful? Give feedback.
-
|
@KajSzy We've currently closed the Early Access programme for Branching. If you have already upgraded expecting access, if you could send in a support request and we'll look into it 😄. I think some of our docs have not been updated to make it clear that it's in private early access, and we've now closed accepting any more requests. I'll update the docs today to be more clear. |
Beta Was this translation helpful? Give feedback.
-
|
Hope you're all doing great! I've been working with supabase on a project for 2 months and noticed something I wanted to share with you that would cause issues for supabase branching. As our projects grow, our seed file (you know, the trusty I've been sidestepping this by ditching the massive seed file and scripting my local database seeding instead. It's a lot like how migrations work: each file is timestamped and has a quick description, and they run in a set order. This means I have separate files for different seeding needs, like permission tables and location table inserts broken down into 1K-insert chunks – it’s pretty neat. Currently, Supabase runs whatever is in I reckon this could be something worth considering for your roadmap for seeding a branch. Thanks for all the hard work you've been putting into Supabase, and I'm excited to see how branching evolves! |
Beta Was this translation helpful? Give feedback.
-
|
Neat idea. I also mentioned this to @sweatybridge who is one of the developers managing our migration/seed runner. I suppose it would have to be timestamped for it to work correctly. Do we know of any other tools doing this? We can't be the first ones to think of this? 😊 |
Beta Was this translation helpful? Give feedback.
-
|
To be honest I took the idea directly from my experience of working with the ORM Sequelize. Here is a relevant documentation that mention both migrations and seed files: https://sequelize.org/docs/v6/other-topics/migrations/ One thing to note is that their migrations have an up (which is covered by seed.sql) and a down that is not covered by supabase. The down function is if you are to roll back a migration including any data manipulation that was required to complete the migration. It's very useful when you can't predict how a project will evolve once it's in front of users. Sequelize also handle transactions in their migrations, which makes migrating production databases a lot less intimidating. |
Beta Was this translation helpful? Give feedback.
-
|
There is a similar discussion to this here as well now 🙌 |
Beta Was this translation helpful? Give feedback.
-
|
Hasura uses timestamped seed files. https://hasura.io/docs/2.0/migrations-metadata-seeds/manage-seeds/ |
Beta Was this translation helpful? Give feedback.
-
|
if new branch is created, new Supabase url for client is reserved on new branch?? I maen if I use following url on main branch Can I use a different url for a new branch like staging? For example, |
Beta Was this translation helpful? Give feedback.
-
|
How it works today is a bit like that but it's the id string in the middle that changes. main branch (production) const supabase = createClient('https://spztrrugbkgdayfejlvi.supabase.co/', 'public-anon-key')the feature branch your working on will then have a completely different id in the url const supabase = createClient('https://qrelykancvxikefwrefd.supabase.co/', 'public-anon-key')I could understand if this might not be useful in some circumstances, as it makes it harder to build urls based on git branch name in maybe your client or server app. The problem extends to API keys though as well, since every branch in Supabase has it's own unique set of API keys, db password and so on. What do you think @chaos128 ? |
Beta Was this translation helpful? Give feedback.
-
|
It would be okay but I think it would be a little bit inconvenient. It would be better if domain and key are not changed but only pathname is changed based on branch names like I said on question. main branch staging branch feature/test branch |
Beta Was this translation helpful? Give feedback.
-
|
That's interesting. Can see that being a lot more useful and easier to use. Also the keys not changing between Preview Branches is interesting as well - we were mostly concerned with Production and Preview being isolated and concentrated efforts on that and hadn't really investigated on making it easy to switch between Preview branches with predictable URLs and consistent keys. Great suggestion. |
Beta Was this translation helpful? Give feedback.
-
|
@chaos128 how are you using Supabase Branching? |
Beta Was this translation helpful? Give feedback.
-
|
Chiming in here because I would also love to see predictable URLs and consistent keys. We have a Next.js app on Vercel, using Prisma. Our current workflow, without Supabase branching: Our branch That means preview/feature branches create Vercel preview deployments, but have to stay unmigrated (except for staging itself), since we don't want to mess up the staging db before merging to If we turned on Supabase branching on our staging db, I'm picturing that it could work for preview deployments if the app and, separately, the GH action, can both get or construct the branch db's URL/creds (actually we use the full pooler URL) from env variables that are available. And then we'd have the GH action migrate the designated branch db upon branch creation. So a completely new set of URL/creds seems hard to deal with in this scenario, whereas some combination of base URL (already set in Vercel and GH) plus the branch name (already easily available in Vercel and GH) would be very doable. I see someone else who posted has a similar setup with some steps to make it theoretically work in the GH action.. but it seems to rely on CLI commands, and I'm not sure if that would work for getting the Vercel preview app to also point to the branch db. (Update: I also just realized Vercel support is in development which would solve the Vercel half.) |
Beta Was this translation helpful? Give feedback.
-
|
Can branching be used as a "dev" environment? |
Beta Was this translation helpful? Give feedback.
-
|
Yep. What's your use case? Can you tell us more? |
Beta Was this translation helpful? Give feedback.
-
|
According to the docs: "The database is only seeded once, when the preview branch is created. To rerun seeding, delete the preview branch and recreate it." But when I deleted and recreated the branch (
|
Beta Was this translation helpful? Give feedback.
-
|
EDIT: |
Beta Was this translation helpful? Give feedback.
-
|
That's probably a bug. We are using github webhooks and I think it only adds the PR metadata to the Preview Branch when a PR is opened (there's a webhook event for it) - but that makes it impossible for a new Preview Branch to then be associated with a PR later; like when you've made a new Preview Branch. I think we could fix that. Everything should work as normal though, it's only the UI here that's been impacted. |
Beta Was this translation helpful? Give feedback.
-
|
So far pretty good with supabase branching. Should I disable my existing github actions that migrate the production database when merging to the production branch? Is it expected that the migrations should be applied via this new Supabase branching integration? |
Beta Was this translation helpful? Give feedback.
-
|
It's worth stressing first that Branching is not suitable for production based apps right now. With that in mind, and if you want to continue; yes, you should be able to merge your feature git branch into your 'production' git branch and it will run the new migration files against the Production Supabase branch. There is currently no way to turn this off, so it's probably advised to disable your github actions. |
Beta Was this translation helpful? Give feedback.
-
|
@MildTomato are there known issues we should watch out for w.r.t. production? Or is it just that more time is needed to bash the bugs out that in theory could harm a prod instance? |
Beta Was this translation helpful? Give feedback.
-
|
When you say it's not suitable for production based apps, do you mean using branches at all, or running prod off of a branch? |
Beta Was this translation helpful? Give feedback.
-
|
@MildTomato does supabase branching support monorepos? Our |
Beta Was this translation helpful? Give feedback.
-
|
Yeah would love to see this sort of mono-repo support! Very excited for you all to start using branching on internally too! |
Beta Was this translation helpful? Give feedback.
-
|
I would also require the mono-repo support for my project with a custom path to my migrations folder. Big fan of this branching feature and how it is progressing! |
Beta Was this translation helpful? Give feedback.
-
|
The code for it is already written and we're going to test everything in upcoming week :) |
Beta Was this translation helpful? Give feedback.
-
|
Monorepo support has been added and is already live if you have an access to branching 🎉 |
Beta Was this translation helpful? Give feedback.
-
|
monorepo support:
|
Beta Was this translation helpful? Give feedback.
-
|
any advice on how to handle issues like this that require setting up things in the database (eg. webhooks)? 
|
Beta Was this translation helpful? Give feedback.
-
|
Any updates here? This is preventing us from using branching |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
For what it's worth, I have been running into so many issues with branching that the best solution for us was to manage the full lifecycle using a custom github action leveraging the management API. |
Beta Was this translation helpful? Give feedback.
-
|
@blechatellier that may be what we have to end up doing—would be a shame |
Beta Was this translation helpful? Give feedback.
-
|
To be fair, hard for them to come up with something that will work for everyone - it's been the best decision and took a couple of days to get it to work. |
Beta Was this translation helpful? Give feedback.
-
|
Hello! Loving the concept so far. After spending some time working around issues (seeding not being run and functions not being deployed), I realised you have a CLI for managing branches (which looks great btw!), and I think it could be highlighted more, as I was under the impression that only the "managed" workflows were supported (i.e only Github + Vercel), but atleast for me the feature set is complete enough that I could run this anywhere (and if i missed that that was possible, many others probably have too) |
Beta Was this translation helpful? Give feedback.
-
|
@sweatybridge any updates on Webhooks? |
Beta Was this translation helpful? Give feedback.
-
|
Yup, we've finally shipped a secure way to use secrets from webhooks supabase/cli#1190 (comment) |
Beta Was this translation helpful? Give feedback.
-
|
I'm facing the same issue as @sleakchat; when I pull my production database schema as a migration using |
Beta Was this translation helpful? Give feedback.
-
|
@baballev we should have documented it better, but you need to enable webhooks via config.toml |
Beta Was this translation helpful? Give feedback.
-
|
Wow great, thanks @sweatybridge this does the trick indeed! :) |
Beta Was this translation helpful? Give feedback.
-
|
We are in dire need of selecting non root directories as the Supabase root. We are using a monorepo with TurboRepo. |
Beta Was this translation helpful? Give feedback.
-
|
It's coming. Bear with us some more time, we're getting there :) |
Beta Was this translation helpful? Give feedback.
-
|
That's great news! We just finished building our own internal psuedo-branching by creating a new project on every PR. It was quite difficult to implement correctly since there was a silent failure when connecting via IPv4. Do you have any rough estimation on timelines? |
Beta Was this translation helpful? Give feedback.
-
|
We're hoping to release this month, but I don't want to be held accountable for any specific date just yet. |
Beta Was this translation helpful? Give feedback.
-
|
Monorepo support has been added and is already live if you have an access to branching 🎉 |
Beta Was this translation helpful? Give feedback.
-
|
Currently, we're testing each branch by setting up a local supabase instance in GH Actions for every run. But that setup takes a significant amount of time compared to the actual test run. The flow that we have in mind is:
Are there any blockers that we should be aware of? Moreover, once this is set up and the Vercel app is used, I'm assuming the preview instances will use the new branched supabase. We also don't want any changes in the preview branches going back into main (which I assume will not happen as we are not using supabase migrations in the preview branches). Can you please confirm this? |
Beta Was this translation helpful? Give feedback.
-
Yes that is correct. The Supabase GitHub integration only look for files in Overall your approach sounds sane to me. We will need to make some changes for step 2 and 3 so that you can fetch a preview branch by its git branch name. Otherwise the current workaround is to parse the output from You might also need to handle retries in step 4 until the status of your branch database is ACTIVE_HEALTHY. I think step 7 is not required if you use the Supabase GitHub integration. Because we delete the branch on PR close. |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I'm doing this approach in a Github Action that always wait until the database is ACTIVE_HEALTHY before continuing. I have retry logic in my github action and it typically is able to connect after a few tries in approximately 10 seconds. Sometimes the Github action fails after like 5 mins, but I then I re-run it and it works. I have had better success by not using Here, I get error message: But sometimes, Github can never seem to connect to the created database so I delete it and try again. |
Beta Was this translation helpful? Give feedback.
-
|
Feedback/idea: It'd be nice (or even crucial) for the preview branch to copy most local and/or production branch settings. Examples:
|
Beta Was this translation helpful? Give feedback.
-
|
I just tested edge function secrets and it turns out you can use the following in [edge_runtime.secrets]
STRIPE_API_KEY = "env(STRIPE_API_KEY)"Locally, the environment variables are populated via I haven't found any official documentation on this behavior, except for some commented-out lines in the example config.toml. Use this approach with caution unless we get confirmation from the supabase maintainers that this is the correct way to do it. |
Beta Was this translation helpful? Give feedback.
-
|
I found what seems to be a bug on the permanent Branching deployment, related to what has been discussed here, @sweatybridge. Encrypted env vars do not get updated to the correct value in the .env.{preview|production}, neither in Vault and Edge Function secrets. The reproduction steps are:
Result:
Unless I'm doing something wrong (I followed all guides and examples), this is quite a critical thing and breaks my backend on every pull request. What do you think? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @GorkaMM, we have identified the bug on our side. It is currently causing dotenvx encrypted secrets to be ignored where it should be used as the source of truth. I will update again when the fix is released (likely next monday). |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @sweatybridge! Reported here: supabase/cli#3742 Is there any workaround in the meantime? I need to launch this weekend. |
Beta Was this translation helpful? Give feedback.
-
|
FYI, this was a bug in Supabase and it was fixed already. |
Beta Was this translation helpful? Give feedback.
-
|
For some reason I'm not seeing migrations running or seed data populated for a preview branch (feature or development). When I create a PR, it's spinning up the branch, just no tables or seed data. |
Beta Was this translation helpful? Give feedback.
-
Done, you can use it today.
There is basic seeding capability already with |
Beta Was this translation helpful? Give feedback.
-
+1(00) on this point! |
Beta Was this translation helpful? Give feedback.
-
|
They say the best way now is to create a separate Supabase project for the staging branch. |
Beta Was this translation helpful? Give feedback.
-
|
Q: We have few ideas how to go around it, but just to get a feel for it in public, wdyt is your preference in regards to long-lived branches?
|
Beta Was this translation helpful? Give feedback.
-
|
Adding a data point: we are using a separate project for Staging + Preview branches, while keeping our original project for Production only (same as @RobSchilderr's post above). This seems to work pretty well for persisting Staging so far, though it's not 1:1 with the Vercel style of branching. |
Beta Was this translation helpful? Give feedback.
-
|
We handle our migrations via Prisma migrate. Are there any plans to support the |
Beta Was this translation helpful? Give feedback.
-
|
Currently you'd have to move file to |
Beta Was this translation helpful? Give feedback.
-
|
Would just moving the folder work? The migration files/formats are directly compatible with supabase? |
Beta Was this translation helpful? Give feedback.
-
|
Yes, the migration file is always just a smallest sql snippet that will result in the desired schema shape at the end of execution. find . -type d -depth 1 | xargs -I{} cp {}/migration.sql migrations/{}.sql; |
Beta Was this translation helpful? Give feedback.
-
|
Got it. A cleaner way built in to supabase would be nice! Especially since there's a pretty large audience (I'm assuming) of supabase TS users using prisma. |
Beta Was this translation helpful? Give feedback.
-
|
Here's a bash script for those that want to copy Prisma migrations to a #!/bin/bash
# Define paths
PRISMA_MIGRATIONS_DIR="./prisma/migrations" # Replace with your Prisma migrations directory
SUPABASE_MIGRATIONS_DIR="./supabase/migrations" # Replace with your desired Supabase migrations directory
# Create the Supabase migrations directory if it doesn't exist
mkdir -p "$SUPABASE_MIGRATIONS_DIR"
# Function to convert Prisma migration files to Supabase format
convert_prisma_to_supabase() {
for prisma_migration_dir in "$PRISMA_MIGRATIONS_DIR"/*/; do
if [[ -d "$prisma_migration_dir" ]]; then
migration_file="$prisma_migration_dir/migration.sql"
if [[ -f "$migration_file" ]]; then
migration_name=$(basename "$prisma_migration_dir")
supabase_migration_file="$SUPABASE_MIGRATIONS_DIR/$migration_name.sql"
cp "$migration_file" "$supabase_migration_file"
echo "Converted $migration_file to $supabase_migration_file"
fi
fi
done
}
# Run the conversion function
convert_prisma_to_supabase
echo "Migration conversion completed."
|
Beta Was this translation helpful? Give feedback.
-
|
Hey Folks I want to Setup a Supa Base Branching for the Automation Testing so the scenario is Below So how i can do it can anyone help me out in this Thanks in Advance. |
Beta Was this translation helpful? Give feedback.
-
|
Would it be possible to add something to |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the suggestion. We plan to make it configurable via GitHub integration settings on our dashboard. |
Beta Was this translation helpful? Give feedback.
-
|
Hello everyone I am here new i want to know that here was for my project recently which was created based on Health care website so i want to know that how should we basically setup proper frontend and supabase properly i am here new and now for these project i am ooking for long term as business if there any issues come in future this is will be secure or not I want to know |
Beta Was this translation helpful? Give feedback.
-
|
I think I'm following what you're asking. And it seems as though your question is about setting up the front end. And honestly just using a react plus shad CN should get you going. Also, for branching, I presume you understand that you need to have the GitHub plus versail plus super base integration all working properly. |
Beta Was this translation helpful? Give feedback.
-
|
While the branching idea is a great one, it fails for a variety of reasons:
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the feedback. We will likely revisit auth configuration towards the end of 2025. Our current solution is to connect your branches to your GitHub repo so that auth configs are synced with each new branch. You may refer to our example for more details. |
Beta Was this translation helpful? Give feedback.
-
|
I am checking in on timing for SMTP settings being a part of the automated branch setup. Not sure where this ranks amongst all the other things going on here for this amazing Supabase feature. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for checking in. We are currently ironing out corner cases with schema diffing. Getting auth config automatically setup on branches will likely come next. Currently our supported way to sync auth config is via GitHub integration. You may refer to our example on how to configure it. |
Beta Was this translation helpful? Give feedback.
-
|
use dashboard create branch, it shows |
Beta Was this translation helpful? Give feedback.
-
|
Could you try |
Beta Was this translation helpful? Give feedback.
-
|
We've found the issue and will be fixing it shortly supabase/cli#4145 |
Beta Was this translation helpful? Give feedback.
-
|
Hi I am still having this exact same issue even now. |
Beta Was this translation helpful? Give feedback.
-
|
Could you try the following steps to rectify
|
Beta Was this translation helpful? Give feedback.
-
|
I've had this issue since branching was in beta where I started setting up branching and got confused by the on boarding flow. I ended up naming my 'production' branch: 'dev', thinking I was creating my first new branch, not my production branch. 
There appears to be no way to change it. I've configured the main branch on my git integration to point at 'main' but there is this name 'dev' stuck in supabase. This has honestly prevented me from using branching more because I assumed I'm going to get super confused about what branch I'm actually working with at some point. |
Beta Was this translation helpful? Give feedback.
-
|
You can rename it via cli command supabase branches update dev --name main --project-ref <ref> |
Beta Was this translation helpful? Give feedback.
-
|
THANK YOU! |
Beta Was this translation helpful? Give feedback.
-
|
There is a strange artifact we are observing. When the github integration & supabase bot/app leaves a comment on the PR & creates preview branches, the storage schema is different. It looks like this When I make a preview branch from the dashboard or from cli, the storage schema is ok. 
This is causing some of our simple migrations to fail in preview branches created by the supabase bot/app as the column doesnt exist |
Beta Was this translation helpful? Give feedback.
-
|
@sweatybridge any ideas? |
Beta Was this translation helpful? Give feedback.
-
|
There is definitely something acting up in the branch creation. It isn't to do with CLI or the Management API. Sometimes the branch is created with a good schema in storage. Sometimes it is created with a bad storage schema We had a PR which randomly created a branch with a broken storage schema. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reporting this. Our team is actively looking into this. Do you have the ref of the branch with bad schema? |
Beta Was this translation helpful? Give feedback.
-
|
@sweatybridge https://supabase.com/dashboard/project/tjtugunnilumzkpgkfbf (although we deleted it.. not sure if you can pull it from that) |
Beta Was this translation helpful? Give feedback.
-
|
Hello, I'm experiencing flakiness when creating branches w/ the CLI, The command always creates a branch that, within a few minutes, is in But then, after waiting until it is ACTIVE_HEALTHY before executing The error is However for some branches, the I've tried instead not linking and directly using |
Beta Was this translation helpful? Give feedback.
-
It will be more robust to wait for branch status to be This is definitely not very intuitive though and we will work on improving it.
This is rather unusual. Could you create a support ticket the next time you observe such failure? We need the failed branch to exist to help debug. |
Beta Was this translation helpful? Give feedback.
-
|
Is it possible to have supabase branches point to a different git repo instead of branches within a single git repo? |
Beta Was this translation helpful? Give feedback.
-
|
Just curious. What purpose would this serve? |
Beta Was this translation helpful? Give feedback.
-
|
You are right this could probably be fixed with having a better git/cicd/db setup. FWIW my use case is I use github pages to host a static website. The problem I ran into using github pages is that you can only have one url per repo. So when i needed to host a staging site I had to fork my repo. Eventually the site grew in complexity and now I need a db. Everything is fine for now with both staging and prod site point to the same db, but eventually the staging site will need to have its own tables so when someone screws around on it the prod site is not affected. |
Beta Was this translation helpful? Give feedback.
-
|
Supabase branches are currently mapped one-to-one with git branch. It's unlikely that we will change this model to support branches to different git repos. Having you considered using vercel or cloudflare pages to host your frontend? Both support different URLs per git branch natively. |
Beta Was this translation helpful? Give feedback.
-
|
Potential Bug When I create a branch on the dashboard, and make any changes to that branch, then open a merge request, that merge request always looks like -- ...
-- A BUNCH OF VALID MIGRATIONS ABOVE HERE
drop trigger if exists "enforce_bucket_name_length_trigger" on "storage"."buckets";
drop trigger if exists "objects_delete_delete_prefix" on "storage"."objects";
drop trigger if exists "objects_insert_create_prefix" on "storage"."objects";
drop trigger if exists "objects_update_create_prefix" on "storage"."objects";
drop trigger if exists "prefixes_create_hierarchy" on "storage"."prefixes";
drop trigger if exists "prefixes_delete_hierarchy" on "storage"."prefixes";Essentially, a bunch of valid migrations followed by these random And when I attempt to merge it, the migrations fail with the following error Anyone else having this issue or know how to resolve? |
Beta Was this translation helpful? Give feedback.
-
|
Anyone got any thoughts on this? |
Beta Was this translation helpful? Give feedback.
-
|
This is due to mismatched storage migration versions between your production and dev branch. It could happen during a gradual rollout of new storage migration on our side. Usually it resolves after a few days without intervention. If the problem persists, could you open a support ticket so we can take a closer look? |
Beta Was this translation helpful? Give feedback.
-
|
If a migration doesn't apply to the main branch, there doesnt seem to be a way to get error notification messages. I'd like to know if the workflow failed for whatever reason. After some debugging as to why the dB was not acting correctly, we realized migrations had failed to apply after a github PR merge. 
Is there any way to get email/webhook notifications about these migrations failing.. 
There seems to be some secret API endpoint 
If we don't have webhooks, can we at least get some docs so we can have a github action poll the workflow running on merge or something? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback. Adding webhook notifications is on our list of priorities. We do have an example using GitHub action to poll branch status. You can probably add a slack notification after that. |
Beta Was this translation helpful? Give feedback.
-
|
Hmm. but this doesnt really allow me to check my production dB migration got applied ok. This is only to check the branch itself. I want to know after merge the migration applied in production as well. The parent project |
Beta Was this translation helpful? Give feedback.
-
|
You can add |
Beta Was this translation helpful? Give feedback.
-
I'm trying to create a branch within Supabase PROD and I am seeing this error.
My setup currently creates new branches via a new PR perfectly every time. Wondering if there is a configuration here on your side that is blocking this from happening. |
Beta Was this translation helpful? Give feedback.
-
|
I tried:
What is in my control: |
Beta Was this translation helpful? Give feedback.
-
|
@fatherkam is there any other branch or project linked with main? IIRC, that caused an error for me once |
Beta Was this translation helpful? Give feedback.
-
|
I have the GitHub Plus versail plus super Bass integration setup so that every time I submit a new PR a new super Bass instance is created. That is the only thing that is linked to this super Base project. If those integrations are a blocker, I'm just going to produce small change PR and then just use the super base instance that is created for that to circumvent this bug |
Beta Was this translation helpful? Give feedback.
-
|
I have the GitHub Plus versail plus super Bass integration setup so that every time I submit a new PR a new super Bass instance is created. That is the only thing that is linked to this super Base project. If those integrations are a blocker, I'm just going to produce small change PR and then just use the super base instance that is created for that to circumvent this bug |
Beta Was this translation helpful? Give feedback.
-
|
@fatherkam you can only create 1 Supabase branch per git branch. Since the default production branch is set to |
Beta Was this translation helpful? Give feedback.
-
|
@sweatybridge is branch creation down? multiple ci cd pr pipelines that were working started failing on branch creations or migrations. Nothing on supabase status. 
https://supabase.com/dashboard/project/utbqyoljckhpypteosjq |
Beta Was this translation helpful? Give feedback.
-
|
There isn't any outage atm. It seems like your first project utbqyoljckhpypteosjq is running fine. The second project lvvkqyhpjlsbstyfyowb was getting 403 forbidden resource error when trying to update status. Could you try pushing to this branch again? |
Beta Was this translation helpful? Give feedback.
-
|
I'd really like to be able to create a database branch independent of a git branch. I was hoping to use it to test some potentially slow, complicated data transformations that are not ready to be committed or run on the production database. Instead I'll need to find a different approach. |
Beta Was this translation helpful? Give feedback.
-
|
You can do this today via the dashboard. Top right -> Feature previews -> Branching via dashboard -> Enable After that, in the create new branch modal, you should see an option to include production data in your branch. |
Beta Was this translation helpful? Give feedback.
-
|
Ah, didn't have that enabled. Just tried but it failed during the data migration:
There is a corresponding error in the source database Postgres logs:
I've since removed this testing branch/project, for reference. |
Beta Was this translation helpful? Give feedback.
-
|
This might be a silly question, and I have searched this page. We are playing with the Dashboard Branch preview feature without github attached right now for a new small project without local dev environments. We can not figure out how to create a Merge Request if there is no github integration in the UI.
|
Beta Was this translation helpful? Give feedback.
-
|
Nevermind, i figured it out.. i needed to enable the preview feature on the branch as well in the ui |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This discussion is for tracking feedback and possible issues for Supabase Branching.
This will help us plan a roadmap for the feature going forward.
Vote for hosting provider integrations here and Git providers here.
Beta Was this translation helpful? Give feedback.
All reactions