Merge branch 'anni/wb-checkruns' of https://github.com/cloudflare/cloudflare-docs into anni/wb-checkruns

Author: aninibread

src/content/docs/pages/configuration/git-integration/github-integration.mdx

@@ -3,7 +3,7 @@ pcx_content_type: concept
 title: GitHub integration
 ---
 
-Cloudflare supports connecting Cloudflare Pages to your GitHub repositories, and will automatically deploy your code everytime you push a change to a branch.
+You can connect each Cloudflare Pages project to a GitHub repository, and Cloudflare will automatically deploy your code every time you push a change to a branch.
 
 ## Features
 
@@ -19,7 +19,7 @@ You can also use [preview deployments](/pages/configuration/preview-deployments/
 
 Every time you open a new pull request on your GitHub repository, Cloudflare Pages will create a unique preview URL, which will stay updated as you continue to push new commits to the branch. Note that preview URLs will not be created for pull requests created from forks of your repository. Learn more in [Preview Deployments](/pages/configuration/preview-deployments/).
 
-![GitHub Preview Urls](~/assets/images/pages/configuration/ghpreviewurls.png)
+![GitHub Preview URLs](~/assets/images/pages/configuration/ghpreviewurls.png)
 
 ### Skipping a build via a commit message
 
@@ -73,7 +73,7 @@ Note that removing access to GitHub will disable new builds for Workers and Page
 
 ### Reinstall the Cloudflare GitHub app
 
-When encountering Git integration related issues, one potential troubleshooting step is attempting to uninstall and reinstall the GitHub application associated with the Cloudflare Pages installation.
+If you see errors where Cloudflare Pages cannot access your git repository, you should attempt to uninstall and reinstall the GitHub application associated with the Cloudflare Pages installation.
 
 1. Go to the installation settings page on GitHub:
    - Navigate to **Settings > Builds** for the Pages project and click **Manage** under Git Repository.

src/content/docs/pages/configuration/git-integration/gitlab-integration.mdx

@@ -3,7 +3,7 @@ pcx_content_type: concept
 title: GitLab integration
 ---
 
-Cloudflare supports connecting Cloudflare Pages to your GitLab repositories, and will automatically deploy your code everytime you push a change to a branch.
+You can connect each Cloudflare Pages project to a GitLab repository, and Cloudflare will automatically deploy your code every time you push a change to a branch.
 
 ## Features
 

src/content/docs/pages/configuration/git-integration/index.mdx

@@ -3,13 +3,13 @@ pcx_content_type: concept
 title: Git integration
 ---
 
-Cloudflare supports connecting Cloudflare Pages to your [GitHub](/pages/configuration/git-integration/github-integration) and [GitLab](/pages/configuration/git-integration/gitlab-integration) repositories, and will automatically deploy your code everytime you push a change to a branch.
+You can connect each Cloudflare Pages project to a [GitHub](/pages/configuration/git-integration/github-integration) or [GitLab](/pages/configuration/git-integration/gitlab-integration) repository, and Cloudflare will automatically deploy your code every time you push a change to a branch.
 
 :::note
 Cloudflare Workers now also supports Git integrations to automatically build and deploy Workers from your connected Git repository. Learn more in [Workers Builds](/workers/ci-cd/builds/).
 :::
 
-Using Git integration with Cloudflare also provides:
+When you connect a git repository to your Cloudflare Pages project, Cloudflare will also:
 
 - **Preview deployments for custom branches**, generating preview URLs for a commit to any branch in the repository without affecting your production deployment.
 - **Preview URLs in pull requests** (PRs) to the repository.
@@ -31,7 +31,9 @@ If you using a different Git provider (e.g. Bitbucket) or a self-hosted instance
 
 ## Add a Git integration
 
-If you don't have a Git account linked to your Cloudflare account, you'll be prompted to set up an installation to GitHub or GitLab when [connecting to Git](/pages/get-started/git-integration/) for the first time, or when adding a new Git account. Follow the prompts and authorize the Cloudflare Git integration.
+## Add a Git integration
+
+If you do not have a Git account linked to your Cloudflare account, you will be prompted to set up an installation to GitHub or GitLab when [connecting to Git](/pages/get-started/git-integration/) for the first time, or when adding a new Git account. Follow the prompts and authorize the Cloudflare Git integration.
 
 You can check the following pages to see if your Git integration has been installed:
 
@@ -42,6 +44,8 @@ For details on providing access to organization accounts, see the [GitHub](/page
 
 ## Manage a Git integration
 
+## Manage a Git integration
+
 You can manage the Git installation associated with your repository connection by navigating to the Pages project, then going to **Settings** > **Builds** and selecting **Manage** under **Git Repository**.
 
 This can be useful for managing repository access or troubleshooting installation issues by reinstalling. For more details, see the [GitHub](/pages/configuration/git-integration/github-integration/#managing-access) and [GitLab](/pages/configuration/git-integration/gitlab-integration/#managing-access) guides.
@@ -55,3 +59,59 @@ If you are using a Git-integrated project and do not want to trigger deployments
 3. You can also change your Preview branch to **None (Disable automatic branch deployments)** to pause automatic preview deployments.
 
 Then, you can use Wrangler to deploy directly to your Pages project and make changes to your Git repository without automatically triggering a build.
+
+## Troubleshooting
+
+If your git integration is experiencing issues, you may find the following banners in the Deployment page of your Pages project.
+
+### Project Creation
+
+#### `This repository is being used for a Cloudflare Pages project on a different Cloudflare account.`
+
+You cannot use the same GitHub/GitLab repository with multiple Cloudflare accounts. To use a Pages project with a different Cloudflare account, delete it from the current Cloudflare account first.
+
+### Deployments
+
+If you run into any issues related to deployments or failing, check your project dashboard to see if there are any SCM installation warnings listed as shown in the screenshot below.
+
+![Pausing a deployment in the Settings of your Pages project](~/assets/images/pages/platform/git.dashboard-error.png)
+
+To resolve an error displayed in the Cloudflare Pages dashboard, find it below and follow the instructions.
+
+#### `This project is disconnected from your Git account, this may cause deployments to fail.`
+
+To resolve this issue, follow the steps provided above in the [Reinstalling a Git installation section](/pages/configuration/git-integration/#reinstall-a-git-installation) for the applicable SCM provider. If the issue persists even after uninstalling and reinstalling, contact support.
+
+#### `Cloudflare Pages is not properly installed on your Git account, this may cause deployments to fail.`
+
+To resolve this issue, follow the steps provided above in the [Reinstalling a Git installation section](/pages/configuration/git-integration/#reinstall-a-git-installation) for the applicable SCM provider. If the issue persists even after uninstalling and reinstalling, contact support.
+
+#### `The Cloudflare Pages installation has been suspended, this may cause deployments to fail.`
+
+Go to your GitHub installation settings:
+
+- `https://github.com/settings/installations` for individual accounts
+- `https://github.com/organizations/<YOUR_ORGANIZATION_NAME>/settings/installations` for organizational accounts
+
+Click **Configure** on the Cloudflare Pages application. Scroll down to the bottom of the page and click **Unsuspend** to allow Cloudflare Pages to make future deployments.
+
+#### `The project is linked to a repository that no longer exists, this may cause deployments to fail.`
+
+You may have deleted or transferred the repository associated with this Cloudflare Pages project. For a deleted repository, you will need to create a new Cloudflare Pages project with a repository that has not been deleted. For a transferred repository, you can either transfer the repository back to the original Git account or you will need to create a new Cloudflare Pages project with the transferred repository.
+
+#### `The repository cannot be accessed, this may cause deployments to fail.`
+
+You may have excluded this repository from your installation's repository access settings. Go to your GitHub installation settings:
+
+- `https://github.com/settings/installations` for individual accounts
+- `https://github.com/organizations/<YOUR_ORGANIZATION_NAME>/settings/installations` for organizational accounts
+
+Click **Configure** on the Cloudflare Pages application. Under **Repository access**, ensure that the repository associated with your Cloudflare Pages project is included in the list.
+
+#### `There is an internal issue with your Cloudflare Pages Git installation.`
+
+This is an internal error in the Cloudflare Pages SCM system. You can attempt to [reinstall your Git installation](/pages/configuration/git-integration/#reinstall-a-git-installation), but if the issue persists, [contact support](/support/contacting-cloudflare-support/).
+
+#### `GitHub/GitLab is having an incident and push events to Cloudflare are operating in a degraded state. Check their status page for more details.`
+
+This indicates that GitHub or GitLab may be experiencing an incident affecting push events to Cloudflare. It is recommended to monitor their status page ([GitHub](https://www.githubstatus.com/), [GitLab](https://status.gitlab.com/)) for updates and try deploying again later.

src/content/docs/pages/get-started/git-integration.mdx

@@ -9,7 +9,7 @@ description: Connect your Git provider to Pages.
 
 import { Details, Render } from "~/components";
 
-In this guide, you will get started with Cloudflare Pages, and deploy your first website to the Pages platform through Git integration. The Git integration enables automatic builds and deployments every time you push a change to your connected [GitHub](/pages/configuration/git-integration/github-integration/) or [GitLab](/pages/configuration/git-integration/gitlab-integration/) repository.
+In this guide, you will get started with Cloudflare Pages and deploy your first website to the Pages platform through Git integration. The Git integration enables automatic builds and deployments every time you push a change to your connected [GitHub](/pages/configuration/git-integration/github-integration/) or [GitLab](/pages/configuration/git-integration/gitlab-integration/) repository.
 
 :::caution[You cannot switch to Direct Upload later]
 If you deploy using the Git integration, you cannot switch to [Direct Upload](/pages/get-started/direct-upload/) later. However, if you already use a Git-integrated project and do not want to trigger deployments every time you push a commit, you can [disable automatic deployments](/pages/configuration/git-integration/#disable-automatic-deployments) on all branches. Then, you can use Wrangler to deploy directly to your Pages projects and make changes to your Git repository without automatically triggering a build.

src/content/docs/workers/ci-cd/builds/build-caching.mdx

@@ -6,7 +6,7 @@ sidebar:
   order: 5
 ---
 
-Improve Workers Builds build times by caching dependencies and build output between builds with a project-wide shared cache.
+Improve Workers build times by caching dependencies and build output between builds with a project-wide shared cache.
 
 The first build to occur after enabling build caching on your Workers project will save relevant artifacts to cache. Every subsequent build will restore from cache unless configured otherwise.
 
@@ -16,7 +16,7 @@ When enabled, build caching will automatically detect which package manager and
 
 The following shows which package managers and frameworks are supported for dependency and build output caching respectively.
 
-### Package Managers
+### Package managers
 
 Workers build cache will cache the global cache directories of the following package managers:
 

src/content/docs/workers/ci-cd/builds/git-integration/github-integration.mdx

@@ -6,7 +6,7 @@ sidebar:
   order: 2
 ---
 
-Cloudflare supports connecting your GitHub repository to your Cloudflare Worker, and will automatically deploy your code everytime you push a change to a selected branch.
+Cloudflare supports connecting your GitHub repository to your Cloudflare Worker, and will automatically deploy your code every time you push a change to a selected branch.
 
 ## Features
 

src/content/docs/workers/ci-cd/builds/git-integration/gitlab-integration.mdx

@@ -6,7 +6,7 @@ sidebar:
   order: 2
 ---
 
-Cloudflare supports connecting your GitLab repository to your Cloudflare Worker, and will automatically deploy your code everytime you push a change to a selected branch.
+Cloudflare supports connecting your GitLab repository to your Cloudflare Worker, and will automatically deploy your code every time you push a change to a selected branch.
 
 ## Features
 

src/content/docs/workers/ci-cd/builds/git-integration/index.mdx

@@ -6,7 +6,7 @@ sidebar:
   order: 3
 ---
 
-Cloudflare supports connecting your [GitHub](/workers/ci-cd/builds/git-integration/github-integration/) and [GitLab](/workers/ci-cd/builds/git-integration/gitlab-integration/) repository to your Cloudflare Worker, and will automatically deploy your code everytime you push a change to a selected branch.
+Cloudflare supports connecting your [GitHub](/workers/ci-cd/builds/git-integration/github-integration/) and [GitLab](/workers/ci-cd/builds/git-integration/gitlab-integration/) repository to your Cloudflare Worker, and will automatically deploy your code every time you push a change to a selected branch.
 
 Adding a Git integration also lets you monitor build statuses directly in your Git provider using [check runs](/workers/ci-cd/builds/git-integration/github-integration/#check-run) or [commit statuses](/workers/ci-cd/builds/git-integration/gitlab-integration/#commit-status), allowing you to manage deployments without leaving your workflow.
 

src/content/docs/workers/ci-cd/builds/troubleshoot.mdx

@@ -25,7 +25,7 @@ The build system uses the `name` argument in the wrangler.toml to determine whic
 :::note
 This does not apply to [Wrangler Environments](/workers/wrangler/environments/) if the Worker name before the `-<env_name>` suffix matches the name in wrangler.toml.
 
-For example, a Worker named `my-worker-staging` on the dashboard can be deployed from a repository that contains a wrangler.toml with the arguemnts `name = my-worker` and `[env.staging]` using the deploy command `npx wrangler deploy --env staging`.
+For example, a Worker named `my-worker-staging` on the dashboard can be deployed from a repository that contains a wrangler.toml with the arguments `name = my-worker` and `[env.staging]` using the deploy command `npx wrangler deploy --env staging`.
 :::
 
 ### Missing wrangler.toml

src/content/docs/workers/get-started/dashboard.mdx

@@ -37,7 +37,7 @@ To create a Workers application:
 
 To do more:
 
-- Push your project to a GitHub or GitLab respoitory then [connect to Builds](/workers/ci-cd/builds/#get-started) to enable automatic builds and deployments.
+- Push your project to a GitHub or GitLab respoitory then [connect to builds](/workers/ci-cd/builds/#get-started) to enable automatic builds and deployments.
 - Review our [Examples](/workers/examples/) and [Tutorials](/workers/tutorials/) for inspiration.
 - Set up [bindings](/workers/runtime-apis/bindings/) to allow your Worker to interact with other resources and unlock new functionality.
 - Learn how to [test and debug](/workers/testing/) your Workers.