## Description Marge Bot currently logs repeated warnings when a pipeline reports the CI status \`waiting_for_resource\`, for example: WARNING Suspicious CI status: 'waiting_for_resource'. ### Example log output 2026-02-01 19:16:51,720 WARNING Suspicious CI status: 'waiting_for_resource'. 2026-02-01 19:17:01,795 WARNING Suspicious CI status: 'waiting_for_resource'. 2026-02-01 19:17:11,867 WARNING Suspicious CI status: 'waiting_for_resource'. 2026-02-01 19:17:21,936 WARNING Suspicious CI status: 'waiting_for_resource'. This state is **expected and legitimate** when GitLab CI/CD **resource groups** are in use. According to the GitLab documentation, jobs can intentionally remain in the \`waiting_for_resource\` state when a \`resource_group\` is configured to limit concurrency (for example, serialized deployment jobs). This behavior is normal and does **not** indicate a stuck or unhealthy pipeline. Relevant documentation: https://docs.gitlab.com/ci/resource_groups/ In these situations: - The job is behaving correctly - The pipeline is not failed or unhealthy - The status resolves automatically once the resource is released ## Expected behavior The `waiting_for_resource` status should **not** be treated as suspicious or logged as a warning. Possible improvements: - Treat `waiting_for_resource` as a neutral / expected CI status - Downgrade the log level from `WARNING` to `INFO` or `DEBUG` - Explicitly whitelist `waiting_for_resource` as a valid CI status This would reduce log noise and avoid false warnings for users relying on resource groups.