feat: Add Tekton CI support in CIQualityGatesAssessor

[mmorhun]

Assisted-by: Claude

Description

Adds basic support for Pipeline-as-Code CI.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement
• Test coverage improvement

Related Issues

N/A

Changes Made

• Check for .tekton directory in the repository config to detect Pipelines-as-Code CI / Konflux
• Check for Tekton pipelines that run on PR
• Unit tests added

Testing

• Unit tests pass (pytest)
• Integration tests pass
• Manual testing performed
• No new warnings or errors

Checklist

• My code follows the project's code style
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published

Screenshots (if applicable)

Additional Notes

Summary by CodeRabbit

• New Features

  • Tekton Pipelines-as-Code support added, enabling detection of pull-request triggers via both annotation-based and expression-based configurations for improved CI quality gates evaluation.

• Tests

  • Comprehensive unit tests added to validate Tekton CI trigger detection across multiple configuration formats and scenarios.

[coderabbitai]

Warning

Rate limit exceeded

@mmorhun has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 22 minutes and 51 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 03530d87-1923-4856-a987-57fd59129512

📥 Commits

Reviewing files that changed from the base of the PR and between 9330f0e and 498c1d3.

📒 Files selected for processing (2)

• src/agentready/assessors/testing.py
• tests/unit/test_assessors_testing.py

📝 Walkthrough

Walkthrough

This PR extends CI quality gates assessment to recognize Tekton Pipelines-as-Code by adding .tekton directory scanning and parsing pipelinesascode.tekton.dev annotations to detect pull-request triggers—supporting both on-event string/array forms and on-cel-expression CEL expressions.

Changes

Tekton PR Trigger Detection

Layer / File(s)	Summary
Tekton PR trigger detection src/agentready/assessors/testing.py, tests/unit/test_assessors_testing.py	Config path .tekton is added to CI scanner, detection logic reads Tekton pipeline YAML and extracts PR triggers from on-event annotations (string and array) and on-cel-expression CEL expressions. Test coverage includes positive cases (simple/array/complex expressions) and negative cases (push-only triggers).

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title follows Conventional Commits format (feat: scope description) and accurately describes the main change: adding Tekton CI support to CIQualityGatesAssessor.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

✨ Simplify code

• Create PR with simplified code

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[mmorhun]

Fixed formatter error.

[github-actions]

📈 Test Coverage Report

Branch	Coverage
This PR	73.7%
Main	73.7%
Diff	✅ +0%

---

Coverage calculated from unit tests only

[mmorhun]

@natifridman @jwm4 could you review the PR?

[jwm4]

Review by Bill Murdock (with assistance from Claude Code)

Verdict: Request changes

The implementation is correct and well-tested. One change needed before merging, plus a few optional suggestions.

Required

docs/attributes.md needs updating. Line 630 enumerates the recognized CI config paths:

A workflow file in .github/workflows/, .gitlab-ci.yml, or similar

Now that .tekton/ is explicitly detected, it should be listed here alongside the others. The "or similar" hand-wave isn't sufficient when the docs already name specific paths.

Suggestions (non-blocking)

1. re.DOTALL on cel_pattern is slightly over-broad. The .* with DOTALL could match on-cel-expression on one line and event == "pull_request" far later in the file (e.g., in a comment or unrelated field). In practice Tekton pipeline files are small and focused, so this is low-risk, but worth noting.

2. Missing integration-level test for detection. The tests verify _has_pr_trigger() directly but don't test that _detect_ci_configs() actually discovers files inside a .tekton/ directory. A test that creates .tekton/pipeline.yaml and calls _detect_ci_configs() would close that gap.

3. Docstring on _has_pr_trigger could be updated. It currently says "Other CI systems (GitLab CI, CircleCI, Travis) run on MRs by default" to explain the return True default. Tekton requires explicit configuration like GitHub Actions, so it's now the second system with explicit trigger detection. A small docstring update would keep it accurate.

Otherwise, nice contribution. The test coverage for annotation formats and CEL expressions is thorough.