Prove the flow

Feature branch → staging

Create an issue, then from staging:

git checkout staging
git pull
git checkout -b feature/hello-preview
# make a small visible change on the home page
git add .
git commit -m "feat: visible preview change for amplify lab

Bump homepage copy so the PR preview is easy to recognize."
git push -u origin HEAD

1. Open a pull request into staging

Open the PR against staging (not main). Link the issue with Closes #N.

Example: jajera/amplify-astro-cicd#4

Close

2. Wait for GitHub CI to pass

Wait until GitHub checks are green (CI build, markdown-lint, commitmsg-conform) and Amplify Web Preview has posted a URL.

Close

3. Confirm the Amplify PR preview

Amplify posts a preview URL on the PR (shape https://pr-<n>.<app-id>.amplifyapp.com). Open it and confirm the homepage marker is visible.

Close

Close

4. Merge the PR

Squash-merge into staging (not main). With GitHub auto-delete head branches on, the feature branch disappears after merge.

Close

Close

5. Confirm staging shows the change

Open https://staging.<app-id>.amplifyapp.com and wait for Amplify to finish deploying staging. Confirm the homepage marker is live.

Close

6. Confirm the preview host is gone

After the feature branch is gone, Amplify disconnects the PR preview. Opening the old https://pr-<n>.<app-id>.amplifyapp.com URL (or the preview branch in the Console) should fail — for example Branch pr-4 not found.

Close

Staging → main

Caution

Before this promote: confirm Restrict deletions is on for staging (or classic Allow deletions off). With Automatically delete head branches enabled, merging staging → main otherwise deletes the Git staging branch (and Amplify auto-disconnection drops the staging host).

1. Open a pull request from staging into main

Promote only after staging looks right. Open the PR into main from staging (not from the feature branch).

Example: jajera/amplify-astro-cicd#5

Close

2. Wait for CI

Wait until required GitHub checks are green. Previews stay off for main, so you should not expect an Amplify Web Preview on this PR.

Close

3. Merge

Squash-merge into main.

Close

4. Confirm main shows the change

In Amplify Hosting, wait until main finishes deploying (status moves from Deploying to successful).

Close

Then open https://main.<app-id>.amplifyapp.com and confirm it matches staging (homepage marker visible).

Close

Tip

Keep a short checklist with your app id and the three URL patterns. Reuse it whenever you teach or screenshot this lab.

Success criteria

• PR preview URL served the feature change
• Staging URL updated after merge to staging
• Main URL updated after merge to main
• Preview host gone (automatic or Console delete)
• No custom domain required

Next: Teardown.