@@ -112,8 +112,8 @@ objects to get the associated project::
112112
113113Reference: https://docs.gitlab.com/ee/ci/triggers/#trigger-token
114114
115- Pipelineschedule
116- =================
115+ Pipelineschedules
116+ ==================
117117
118118You can schedule pipeline runs using a cron-like syntax. Variables can be
119119associated with the scheduled pipelines.
@@ -128,7 +128,10 @@ Reference
128128 +:attr: `gitlab.v4.objects.Project.pipelineschedules `
129129 +:class: `gitlab.v4.objects.ProjectPipelineScheduleVariable `
130130 +:class: `gitlab.v4.objects.ProjectPipelineScheduleVariableManager `
131- +:attr: `gitlab.v4.objects.Project.pipelineschedules `
131+ +:attr: `gitlab.v4.objects.ProjectPipelineSchedule.variables `
132+ +:class: `gitlab.v4.objects.ProjectPipelineSchedulePipeline `
133+ +:class: `gitlab.v4.objects.ProjectPipelineSchedulePipelineManager `
134+ +:attr: `gitlab.v4.objects.ProjectPipelineSchedule.pipelines `
132135
133136* GitLab API: https://docs.gitlab.com/ce/api/pipeline_schedules.html
134137
@@ -188,6 +191,9 @@ Delete a schedule variable::
188191
189192 var.delete()
190193
194+ List all pipelines triggered by a pipeline schedule::
195+
196+ pipelines = sched.pipelines.list()
191197
192198Jobs
193199====