You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/content/docs/pages/configuration/git-integration/github-integration.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,7 +39,7 @@ Check runs will appear like the following in your repository.
39
39
40
40
If a build skips for any reason (i.e. CI Skip, build watch paths, or branch deployment controls), the check run/commit status will not appear.
41
41
42
-
## Managing access
42
+
## Manage access
43
43
44
44
You can deploy projects to Cloudflare Workers from your company or side project on GitHub using the [Cloudflare Workers & Pages GitHub App](https://github.com/apps/cloudflare-workers-and-pages).
Copy file name to clipboardExpand all lines: src/content/docs/pages/configuration/git-integration/gitlab-integration.mdx
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ You can deploy projects to Cloudflare Pages from your company or side project on
43
43
44
44
By authorizing Cloudflare Pages to access your GitLab account, you will automatically allow access to organizations, groups, and namespaces your GitLab account can access for use by Cloudflare Pages. Managing access to these organizations and groups is handled by GitLab.
45
45
46
-
### Removing access
46
+
### Remove access
47
47
48
48
You can remove Cloudflare Workers' access to your GitLab account by navigating to [Authorized Applications page](https://gitlab.com/-/profile/applications) on GitLab. Find the applications called Cloudflare Workers and select the **Revoke** button to revoke access.
Copy file name to clipboardExpand all lines: src/content/docs/pages/configuration/git-integration/index.mdx
-60Lines changed: 0 additions & 60 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,8 +31,6 @@ If you using a different Git provider (e.g. Bitbucket) or a self-hosted instance
31
31
32
32
## Add a Git integration
33
33
34
-
## Add a Git integration
35
-
36
34
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.
37
35
38
36
You can check the following pages to see if your Git integration has been installed:
@@ -44,8 +42,6 @@ For details on providing access to organization accounts, see the [GitHub](/page
44
42
45
43
## Manage a Git integration
46
44
47
-
## Manage a Git integration
48
-
49
45
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**.
50
46
51
47
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.
@@ -59,59 +55,3 @@ If you are using a Git-integrated project and do not want to trigger deployments
59
55
3. You can also change your Preview branch to **None (Disable automatic branch deployments)** to pause automatic preview deployments.
60
56
61
57
Then, you can use Wrangler to deploy directly to your Pages project and make changes to your Git repository without automatically triggering a build.
62
-
63
-
## Troubleshooting
64
-
65
-
If your git integration is experiencing issues, you may find the following banners in the Deployment page of your Pages project.
66
-
67
-
### Project Creation
68
-
69
-
#### `This repository is being used for a Cloudflare Pages project on a different Cloudflare account.`
70
-
71
-
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.
72
-
73
-
### Deployments
74
-
75
-
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.
76
-
77
-
78
-
79
-
To resolve an error displayed in the Cloudflare Pages dashboard, find it below and follow the instructions.
80
-
81
-
#### `This project is disconnected from your Git account, this may cause deployments to fail.`
82
-
83
-
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.
84
-
85
-
#### `Cloudflare Pages is not properly installed on your Git account, this may cause deployments to fail.`
86
-
87
-
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.
88
-
89
-
#### `The Cloudflare Pages installation has been suspended, this may cause deployments to fail.`
90
-
91
-
Go to your GitHub installation settings:
92
-
93
-
-`https://github.com/settings/installations` for individual accounts
94
-
-`https://github.com/organizations/<YOUR_ORGANIZATION_NAME>/settings/installations` for organizational accounts
95
-
96
-
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.
97
-
98
-
#### `The project is linked to a repository that no longer exists, this may cause deployments to fail.`
99
-
100
-
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.
101
-
102
-
#### `The repository cannot be accessed, this may cause deployments to fail.`
103
-
104
-
You may have excluded this repository from your installation's repository access settings. Go to your GitHub installation settings:
105
-
106
-
-`https://github.com/settings/installations` for individual accounts
107
-
-`https://github.com/organizations/<YOUR_ORGANIZATION_NAME>/settings/installations` for organizational accounts
108
-
109
-
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.
110
-
111
-
#### `There is an internal issue with your Cloudflare Pages Git installation.`
112
-
113
-
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/).
114
-
115
-
#### `GitHub/GitLab is having an incident and push events to Cloudflare are operating in a degraded state. Check their status page for more details.`
116
-
117
-
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.
Copy file name to clipboardExpand all lines: src/content/docs/workers/ci-cd/builds/git-integration/gitlab-integration.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,15 +32,15 @@ Check runs will appear like the following in your repository. You can select one
32
32
33
33
Note that when using [build watch paths](/workers/ci-cd/builds/build-watch-paths/), only projects that trigger a build will generate a commit status.
34
34
35
-
## Managing access
35
+
## Manage access
36
36
37
37
You can deploy projects to Cloudflare Workers from your company or side project on GitLab using the Cloudflare Pages app.
38
38
39
39
### Organizational access
40
40
41
41
By authorizing Cloudflare Workers to access your GitLab account, you will automatically allow access to organizations, groups, and namespaces your GitLab account can access for use by Cloudflare Workers. Managing access to these organizations and groups is handled by GitLab.
42
42
43
-
### Removing access
43
+
### Remove access
44
44
45
45
You can remove Cloudflare Workers' access to your GitLab account by navigating to [Authorized Applications page](https://gitlab.com/-/profile/applications) on GitLab. Find the applications called Cloudflare Pages and select the **Revoke** button to revoke access.
0 commit comments