From 0ab195c18a861fa77290d107863a8cc1d3fc1296 Mon Sep 17 00:00:00 2001 From: SamSeed-Softwire <63662292+SamSeed-Softwire@users.noreply.github.com> Date: Tue, 29 Nov 2022 13:30:44 +0000 Subject: [PATCH] docs: rename overall section title Co-authored-by: James Rose --- docs/infrastructure.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/infrastructure.md b/docs/infrastructure.md index 8b9a1b068..a09ccffbc 100644 --- a/docs/infrastructure.md +++ b/docs/infrastructure.md @@ -122,7 +122,7 @@ After a sucessful deployment a comment will be added to the pull request with th Once a pull request has been closed the review app infrastructure will be tore down to save on any costs. Should you wish to re-open a closed pull request the review app will be spun up again. -### Troubleshooting +### How to fix review app deployment failures One reason a review app deployment might fail is that it is attempting to run migrations which conflict with data in the database. For example you might have introduced a unique constraint, but the database associated with the review app has duplicate data in it that would violate this constaint, and so the migration cannot be run. There are 2 main ways to remedy this: