You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/architecture.mdx
+20Lines changed: 20 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -135,6 +135,26 @@ For each rollout, the control plane freezes the required target set immediately
135
135
136
136
With no configured health check, `healthy` means only that the container is running. Routing convergence prevents completion before network configuration is live, but application-level readiness remains the responsibility of a user-configured health check.
137
137
138
+
## Pull Request Preview Isolation
139
+
140
+
An enabled GitHub service represents each eligible pull request as an ordinary,
141
+
visible stateless service in the project's `previews` environment. An existing
142
+
environment with that name is reused; otherwise the control plane creates it.
143
+
The environment remains after its last preview closes and may also contain
144
+
unrelated user-created services.
145
+
146
+
Each copy has an independent service ID, revision, build, rollout, deployment
147
+
set, registry path, and generated route while reusing the normal runtime
148
+
pipeline. It is copied from the base service only when first created, so later
149
+
user edits to the visible preview service survive pull request updates.
150
+
151
+
The control plane resolves the exact synthetic merge ref and queues an ordinary
152
+
build. The latest revision on the copy prevents superseded build and rollout
153
+
callbacks from deploying or reporting success. GitHub reports the transient
154
+
environment as ready only after health and routing convergence complete.
155
+
Closing, merging, or drafting the pull request deletes the copied service after
0 commit comments