Repository navigation
ci: deploy dev to staging and promote reviewed releases to main - #84
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota. Try requesting a review at a lower effort level.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
procoder-ji
left a comment
procoder-ji
left a comment
There was a problem hiding this comment.
Reviewed the branch policy, deployment secret boundaries and OAuth host handling. Live isolated staging checks passed; merge remains gated on the required CI checks.
Route contributions through dev and promote reviewed staging changes to main. Deploy separate frontend/backend projects only after CI and keep staging out of search.
Verified: lint, typecheck, 193 unit tests, branch policy tests, and live staging frontend/backend with Google configured and database-backed sessions.