Git deployment workflow
Review a Preview deployment
Use a stable branch URL and an immutable commit URL to test the exact change under review and communicate useful evidence.
8 minute lesson
A branch can receive many deployments. The branch URL tracks its latest deployment, while a commit-specific URL identifies one exact build.
Open the preview from the pull request or dashboard, verify the source commit, and test the changed paths plus a small regression set. Share the immutable URL when a review comment must remain attached to one version. If protection is enabled, make sure intended reviewers can access it without making private work public.
Review the environment as well as the interface. Confirm the preview uses test data and preview-scoped credentials, then exercise any migration, webhook, scheduled task, or third-party side effect the change touches. A visual approval does not prove those boundaries are safe.
Leave evidence that can be repeated: commit SHA, immutable URL, paths tested, expected results, and any known difference from Production. If another push replaces the branch alias, the review should still point to the artifact it approved. Promote only the exact deployment or source revision that passed.
Update the branch twice. Identify the branch URL and both immutable deployment URLs, then write a short review tied to the latest commit.
Lesson completed