<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary On the main repository page, there is a small “check mark” icon that represents the commit status. When clicking it, GitLab opens the latest pipeline for that commit. The problem is that in this view, GitLab sometimes shows **a pipeline from security scans or background policies, instead of the actual deploy pipeline**. As a result, the commit status shows “passed” even though the real deploy pipeline failed. {width="777" height="144"} This creates confusion for users who trust that commit status as a quick indicator of the project health. <!--Summarize the bug encountered concisely.--> ### Steps to reproduce I haven't been able to reproduce this, but the customer captured a HAR, a short video recording, along with a brief description of their tests Notes from their tests; "at first, in the main window, when we click the commit status it redirects tp the pipeline 28919455, which was triggered by  the Gitlab Security Policy Bot, and in the video it can be seen there are 5 pipelines more related to security. But, what we are expecting is that the pipeline 27669742, triggered by Jason Fernandez, is the the one shown on commit status on the main window" <!--Describe how one can reproduce the issue - this is very important. Please use an ordered list.--> ### Example Project <!--If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version.--> ### What is the current _bug_ behavior? ### Root Cause The badge status logic does not differentiate between pipeline sources. Policy bot pipelines are treated the same as user-triggered deployment pipelines when determining which pipeline to display. The pipeline doesn't always link to an actual deploy pipeline. <!--Describe what actually happens.--> ### What is the expected _correct_ behavior? The commit status badge should: 1. **Link to** user-triggered deployment pipelines (not policy bot pipelines) 2. **Exclude** informational pipeline sources (`security_orchestration_policy`, `pipeline_execution_policy_schedule`) from badge display logic 3. **Preserve visibility** of policy bot pipeline results elsewhere in the UI (pipeline list, MR widgets, etc.) The commit "checkmark" should lead to the deploy pipeline for the latest commit <!--Describe what you should see instead.--> ### Relevant logs and/or screenshots See private comment. <!--Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.--> ### Output of checks <!--If you are reporting a bug on GitLab.com, uncomment below--> <!--This bug happens on GitLab.com--> <!--and uncomment below if you have /label privileges--> <!--/label ~"reproduced on GitLab.com"--> <!--or follow up with an issue comment of `@gitlab-bot label ~"reproduced on GitLab.com"` if you do not--> #### Results of GitLab environment info The customer here is on 18.3.2 <!--Input any relevant GitLab environment information if needed.--> <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: \\\\\\\`sudo gitlab-rake gitlab:env:info\\\\\\\`) (For installations from source run and paste the output of: \\\\\\\`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\\\\\\\`) </pre> </details> #### Results of GitLab application Check <!--Input any relevant GitLab application check information if needed.--> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: \\\`sudo gitlab-rake gitlab:check SANITIZE=true\\\`) (For installations from source run and paste the output of: \\\`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true\\\`) (we will only investigate if the tests are passing) </pre> </details> ### Possible fixes <!--If you can, link to the line of code that might be responsible for the problem.--> ### Patch release information for backports If the bug fix needs to be backported in a [patch release](https://handbook.gitlab.com/handbook/engineering/releases/patch-releases) to a version under [the maintenance policy](https://docs.gitlab.com/policy/maintenance/), please follow the steps on the [patch release runbook for GitLab engineers](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/patch/engineers.md). Refer to the [internal "Release Information" dashboard](https://dashboards.gitlab.net/d/delivery-release_info/delivery3a-release-information?orgId=1) for information about the next patch release, including the targeted versions, expected release date, and current status. #### High-severity bug remediation To remediate high-severity issues requiring an [internal release](https://handbook.gitlab.com/handbook/engineering/releases/internal-releases/) for single-tenant SaaS instances, refer to the [internal release process for engineers](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/internal-releases/engineers.md?ref_type=heads). <!--If you don't have /label privileges, follow up with an issue comment of `@gitlab-bot label ~"type::bug"`-->