From bba0696015c8e1f8dee1c9817267b6b8ffa61fa1 Mon Sep 17 00:00:00 2001 From: Bohdan Pysarenko Date: Fri, 7 Aug 2026 16:44:47 +0300 Subject: [PATCH 1/2] update run pipeline block --- _docs/pipelines/run-pipeline.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/_docs/pipelines/run-pipeline.md b/_docs/pipelines/run-pipeline.md index 6d10dfd4d..298183d29 100644 --- a/_docs/pipelines/run-pipeline.md +++ b/_docs/pipelines/run-pipeline.md @@ -43,6 +43,13 @@ The table below describes the settings in the Triggers page. |**Debug** | Runs the pipeline in debug mode where you can add breakpoints and use the debug terminal. See [Debugging pipelines]({{site.baseurl}}/docs/pipelines/debugging-pipelines/). | |**Run** | Triggers a build with the current settings and takes you to the Builds page where you can monitor the pipeline. See [Monitoring pipelines]({{site.baseurl}}/docs/pipelines/monitoring-pipelines/). | +>**NOTES** +There are a few disclaimers in case of using Gitlab provider + * When a build is triggered manually with a simulated Git trigger, actually, only comitter name (public name) is available to attach build metadata instead of the correct GitLab username when build triggered directly by webhook. It's Gitlab restriction related to committ metadata + * In this case, Codefresh looks up the commit's committer by email through the GitLab API, and matches the result against the committer's name, to display the corresponding GitLab account username instead of the raw committer name recorded in the commit. This avoids the same contributor appearing under multiple different names (for example, a full name on one machine and a GitLab username on another) in build information and committer lists. + * But the lookup depends on the committer's email being visible to the API token used for the GitLab integration. By default, GitLab only exposes a user's _public_ email to non-admin tokens, which the committer must explicitly set on their GitLab profile. + * For self-hosted (on-premises) GitLab instances, if the integration uses a token that belongs to a GitLab instance administrator, the lookup can also match on the account's primary email, not only the public one, making resolution more reliable. + * If Codefresh cannot uniquely match the commit to a GitLab account, for example if the committer has no public email and the token is not an administrator's, or more than one account matches, it falls back to the original committer name recorded in the commit, same as when this behavior is disabled. ## Share build run settings From c7be8128ff96cb89f6eab1a7dd3688f188071b4f Mon Sep 17 00:00:00 2001 From: Bohdan Pysarenko Date: Mon, 10 Aug 2026 10:50:23 +0300 Subject: [PATCH 2/2] fix formatting --- _docs/pipelines/run-pipeline.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_docs/pipelines/run-pipeline.md b/_docs/pipelines/run-pipeline.md index 298183d29..5dda2b236 100644 --- a/_docs/pipelines/run-pipeline.md +++ b/_docs/pipelines/run-pipeline.md @@ -43,7 +43,7 @@ The table below describes the settings in the Triggers page. |**Debug** | Runs the pipeline in debug mode where you can add breakpoints and use the debug terminal. See [Debugging pipelines]({{site.baseurl}}/docs/pipelines/debugging-pipelines/). | |**Run** | Triggers a build with the current settings and takes you to the Builds page where you can monitor the pipeline. See [Monitoring pipelines]({{site.baseurl}}/docs/pipelines/monitoring-pipelines/). | ->**NOTES** +>**NOTES** There are a few disclaimers in case of using Gitlab provider * When a build is triggered manually with a simulated Git trigger, actually, only comitter name (public name) is available to attach build metadata instead of the correct GitLab username when build triggered directly by webhook. It's Gitlab restriction related to committ metadata * In this case, Codefresh looks up the commit's committer by email through the GitLab API, and matches the result against the committer's name, to display the corresponding GitLab account username instead of the raw committer name recorded in the commit. This avoids the same contributor appearing under multiple different names (for example, a full name on one machine and a GitLab username on another) in build information and committer lists.