After successfully deploying and creating the repository and live preview of your store, you can access the Dashboard page for detailed information about your store deploys. The Dashboard displays the current status of your store, including its domains, deployed versions, store preview, and commits.
On the Dashboard page, you will find two main views: Overview and Deploys. For more information about each view, continue reading the next sections.
The Overview section provides information about the production deployment of your store.
Check out the table below for more information:
|Opens a preview of your store in a new tab.
|Opens the deployed version of the store in a new tab.
|Opens the URL of your store's domain, which is the same as the preview.
|Displays the most recent commit to your store's repository, including the date, month, year, and the GitHub user who made the commit.
|Displays the status of the deployment. For more information on the status values, refer to Status available values.
Status available values
The Status field can have one of the following values:
Success: The deployment was successful. If you want to check the commit associated with it, go to the Deploys tab.
Error: An error in the pipeline caused the deploy to fail. To identify the specific step where the error occurred, access the Deploys tab and check the last commit. Then, access your store repository and verify the pipeline related to that commit.Note that a deploy can fail even if the build process is successful. In this case, even though the code compiled correctly, the deploy may have failed in a specific step of the pipeline.
The Deploys section provides a summary of each deployment made in your store's repository.
|Displays the URL to the deploy preview of a specific commit.
|Displays the commit hash associated with a particular commit.
|Displays the date and time of the commit in the format
|Displays the time it took to complete the commit process.
|Indicates the status of the deployment. Possible statuses are
Failed. For more information on the
Failed status, go to the repository and check what failed in the commit.
|Provides an overview of the status of quality checks, including Lighthouse audits and Integration Tests. These checks help you identify and prevent regressions in your store. For more information on the Quality checks values, refer to Quality checks available values. Remember: Lighthouse audits are an essential step in the go-live checklist. Ensure you achieve the recommended score for the lighthouse checks to pass.
|More actions menu (
|Opens a list with the following options after being clicked:
Quality checks available values
The Quality checks field can have one of the following values:
Success: All checks have passed.
Skipped: In the CI process, specific checks were not performed for certain commits. This often occurs when the commit being tested was never the HEAD commit of the main branch, saving time and resources without compromising code quality.
Failed: For more information on the
Failedstatus, go to the repository and check what failed in the commit.
Deleting the project
To delete your FastStore project, click the More actions menu (
⋮). Then, click Delete Project.
A modal to confirm your choice will open.
Proceed with caution. Deleting the project is irreversible and will permanently remove all deployments and domains associated with it.