The backend's Cloud Build trigger (deploys to Cloud Run service nawab-ai in GCP project upai-projects on push to main) was watching LucknowAI/nawabAi2.0 via its GitHub connection — confirmed from the old repo's trigger-config.yaml:
description: Build and deploy to Cloud Run service nawab-ai on push to "^main$"
github:
name: nawabAi2.0
owner: LucknowAI
push:
branch: ^main$That trigger is now dead since the repo is deleted. The frontend almost certainly has an equivalent trigger too (it has its own cloudbuild.yaml), though I did not find an exported config for it to confirm the exact trigger ID.
Needs GCP Console access (I don't have any) to:
- Find and delete/update the stale trigger(s) referencing the deleted repos.
- Reconnect the GitHub App/connection to
LucknowAI/nawab.
- Recreate the trigger(s) pointing at
main, with build context / Dockerfile path updated to backend/ (and frontend/ for the frontend trigger) since those are now subfolders instead of repo roots.
The backend's Cloud Build trigger (deploys to Cloud Run service
nawab-aiin GCP projectupai-projectson push tomain) was watchingLucknowAI/nawabAi2.0via its GitHub connection — confirmed from the old repo'strigger-config.yaml:That trigger is now dead since the repo is deleted. The frontend almost certainly has an equivalent trigger too (it has its own
cloudbuild.yaml), though I did not find an exported config for it to confirm the exact trigger ID.Needs GCP Console access (I don't have any) to:
LucknowAI/nawab.main, with build context / Dockerfile path updated tobackend/(andfrontend/for the frontend trigger) since those are now subfolders instead of repo roots.