Skip to content

Commit 345ecab

Browse files
authored
Add an explanation of how Pages determines whether the user's build command has failed (#16543)
* Add an explanation of how Pages determines whether the user's build command has failed * Fix typo in build-configuration.mdx
1 parent 6b9150c commit 345ecab

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/content/docs/pages/configuration/build-configuration.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Build directories indicates where your project's build command outputs the built
1818

1919
<Details header="Understanding your build configuration">
2020

21-
The build command is provided by your framework. For example, the Gatsby framework uses `gatsby build` as its build command. When you are working without a framework, leave the **Build command** field blank.
21+
The build command is provided by your framework. For example, the Gatsby framework uses `gatsby build` as its build command. When you are working without a framework, leave the **Build command** field blank. Pages determines whether a build has succeeded or failed by reading the exit code returned from the user supplied build command. Any non-zero return code will cause a build to be marked as failed. An exit code of 0 will cause the Pages build to be marked as successful and assets will be uploaded regardless of if error logs are written to standard error.
2222

2323
The build directory is generated from the build command. Each framework has its own naming convention, for example, the build output directory is named `/public` for many frameworks.
2424

0 commit comments

Comments
 (0)