Summary of Changes

Hello @chmouel, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses an issue where invalid Common Expression Language (CEL) expressions in PipelineRuns would lead to duplicate error comments being posted on Pull Requests. By introducing a control mechanism for error reporting within the MatchPipelinerunByAnnotation function, the change ensures that only a single, relevant error notification is provided to users, significantly improving the clarity and reducing noise in PR feedback.

Highlights

• Duplicate CEL Validation Errors: Previously, when a PipelineRun contained an invalid CEL expression, the system would post two identical error comments on the Pull Request. This was due to the MatchPipelinerunByAnnotation() function being invoked twice during the processing flow.
• Controlled Error Reporting: A new boolean parameter, reportErrors, has been introduced to the MatchPipelinerunByAnnotation() function. This parameter provides an explicit switch to control whether CEL validation errors are reported to GitHub, ensuring that error comments are posted only once at the appropriate stage of processing.

🔍 PR Lint Feedback

Note: This automated check helps ensure your PR follows our contribution guidelines.

⚠️ Items that need attention:

🎫 Jira reference

Add a Jira reference in the description using one of the following formats:

• https://issues.redhat.com/browse/SRVKP-<number>

If no SRVKP ticket exists yet, link a GitHub issue instead (e.g., Fixes #123).
Minor housekeeping PRs without Jira coverage can skip this after confirming with reviewers.

🤖 AI attribution

The following commits lack an explicit AI attribution footer:

• 4d7c9e3 fix: Only report CEL validation errors once
• ee64d0c fix: modify repo URL for log collection
• 8a242d4 feat: Add debug logging for pipelineascode
• 7624805 test: Move flaky tests to its own CI job

If no AI assistance was used for a commit, you can ignore this warning.
Otherwise add an Assisted-by: or Co-authored-by: footer referencing the AI used.

ℹ️ Next Steps

• Review and address the items above
• Push new commits to update this PR
• This comment will be automatically updated when issues are resolved

_{🤖 This feedback was generated automatically by the PR CI system}

❌ PR-Agent failed to apply 'global' repo settings

The configuration file needs to be a valid TOML, please fix it.

Error message:
cannot access local variable 'file_data' where it is not associated with a value

[github_app]
pr_commands = [ "/review" ]

[pr_reviewer]
enable_review_labels_security = true
enable_chat_in_code_suggestions=false
enable_chat_in_code_suggestions = false
enable_summary=false
enable_help_text=false

[pr_description]
publish_description_as_comment = true

[pr_code_suggestions]
commitable_code_suggestions = true

[pr_test]
num_tests = 0

/review

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

func MatchPipelinerunByAnnotation(ctx context.Context, logger *zap.SugaredLogger, pruns []*tektonv1.PipelineRun, cs *params.Run, event *info.Event, vcx provider.Interface, eventEmitter *events.EventEmitter, repo *apipac.Repository, reportErrors bool) ([]Match, error) {
	matchedPRs := []Match{}

if len(celValidationErrors) > 0 && reportErrors {
	reportCELValidationErrors(ctx, repo, celValidationErrors, eventEmitter, vcx, event)
}

	statusCount := len(repo.Status)
	if opts.TargetSHA != "" {
		statusCount = 0
		for _, status := range repo.Status {
			if status.SHA != nil && *status.SHA == opts.TargetSHA {
				statusCount++
			}
		}
	}

	clients.Log.Infof("Still waiting for repository status to be updated: %d/%d", statusCount, opts.MinNumberStatus)
	time.Sleep(2 * time.Second)
	return statusCount >= opts.MinNumberStatus, nil
})

/gemini review