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: _docs/integrations/ci-integrations.md
+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
@@ -71,7 +71,7 @@ The table describes _all_ the arguments required for CI integrations in general.
71
71
|`CF_WORKFLOW_NAME`| The name assigned to the workflow that builds the image. When defined, the name is displayed in the Codefresh platform. Example,`Staging step`| Optional|
72
72
|`CF_GIT_BRANCH`| The Git branch with the commit and PR (pull request) data to add to the image. Pass the Branch from the event payload used to trigger your action.| Required|
73
73
|`CF_GIT_REPO`| The Git repository with the configuration and code used to build the image.| Required|
74
-
|`CF_GIT_PROVIDER`| The Git provider for the integration, and can be eitherGitHub, GitLab, Bitbucket, orBitbucket Server.| Required|
74
+
|`CF_GIT_PROVIDER`| The Git provider for the integration, and can be either`github`,`gitlab`,`bitbucket`, or`bitbucket-server`.| Required|
75
75
|`CF_GITHUB_TOKEN`| The GitHub authentication token. The token must have`repo` scope. See[Git tokens]({{site.baseurl}}/docs/reference/git-tokens/).| Required|
76
76
|`CF_GITHUB_API_URL`| The URL to the GitHub developer site.| Required|
77
77
|`CF_BITBUCKET_USERNAME`| The username for the Bitbucket or the BitBucket Server (on-prem) account.| Required|