Merge pull request circleci#7543 from circleci/DOCTEAM-738_project_slug_definition

kbatuigas · web-flow · commit ab95625f370f · 2022-11-10T09:03:05.000-05:00
Ensure consistency in project slug definition
diff --git a/jekyll/_cci2/api-developers-guide.md b/jekyll/_cci2/api-developers-guide.md
@@ -153,7 +153,7 @@ The following section details the steps you would need, from start to finish, to
 ### Prerequisites
 {: #prerequisites }
 
-* A GitHub or Bitbucket account with a repository to set up with CircleCI.
+* A GitHub, Bitbucket, or GitLab account with a repository to set up with CircleCI. **GitLab SaaS users:** Please note the [change in the definition](#gitlab-saas-support-projects) for the project slug references in the examples and use cases on the rest of this document.
 * Completion of the CircleCI [onboarding]({{ site.baseurl }}/getting-started).
 
 ### Steps
diff --git a/jekyll/_cci2/scheduled-pipelines.md b/jekyll/_cci2/scheduled-pipelines.md
@@ -180,7 +180,9 @@ curl --location --request GET "https://circleci.com/api/v2/project/<project-slug
 --header "circle-token: <PERSONAL_API_KEY>"
 ```
 
-`project-slug` takes the form of `vcs-slug/org-name/repo-name`, e.g. `gh/CircleCI-Public/api-preview-docs`.
+For GitHub and Bitbucket users: `project-slug` takes the form of `vcs-type/org-name/repo-name`, e.g. `gh/CircleCI-Public/api-preview-docs`.
+
+For GitLab SaaS Support users: `project-slug` takes the form of `circleci/:slug-remainder`. Refer to the [Getting Started section]({{site.baseurl}}/api-developers-guide/#getting-started-with-the-api) of the API Developer's Guide for more information on the project slug format.
 
 **Q:** Why is my scheduled pipeline not running?
 
