vincerubinetti
commented
2 months ago Maybe one of these will work:
https://github.com/nwtgck/actions-netlify https://github.com/jsmrcaga/action-netlify-deploy
Here is the current site information:
Site information
Site name
gene-plexus
Owner
arjun-krishnan's team
Site ID
6ddb4538-0ece-4d31-af77-c6c5babdac3c
Created
Apr 3 at 1:11 PM
Last update
Yesterday at 5:11 PMRuntime
Not set
Base directory
/
Package directory
Not set
Build command
cd frontend && bun install && bun run build
Publish directory
frontend/dist
Functions directory
netlify/functions
Deploy log visibility
Logs are public
Build status
Active
Currently we host the frontend on Netlify, which is set up to deploy a new production version of the site any time it detects changes on the main branch of this repo. Meanwhile, the backend/cloud functions get pushed to GCP via a workflow run on merging into main, which seems like it can take a long time. During this time, there will be a mismatch between the frontend (deployed almost instantly) on Netlify, and the backend (deployed ~30 min later on GCP). It should be possible to make Netlify "wait" until the GCP upload (this is the part that makes it take long I assume) is done before updating the frontend.
Reading to do: https://answers.netlify.com/t/support-guide-how-can-i-disable-automatic-git-deploys/166/179