Skip to content

Enable ai-integrations workspace in fullsend#3680

Merged
gabemontero merged 1 commit into
redhat-developer:mainfrom
johnmcollier:fullsendaiint
Jul 4, 2026
Merged

Enable ai-integrations workspace in fullsend#3680
gabemontero merged 1 commit into
redhat-developer:mainfrom
johnmcollier:fullsendaiint

Conversation

@johnmcollier

Copy link
Copy Markdown
Member

Hey, I just made a Pull Request!

Enables the ai-integrations workspace to be used with fullsend.

CC @gabemontero @durandom

✔️ Checklist

  • A changeset describing the change and affected packages. (more info)
  • Added or Updated documentation
  • Tests for new functionality and regression tests for bug fixes
  • Screenshots attached (for UI changes)

Signed-off-by: John Collier <jcollier@redhat.com>
@johnmcollier johnmcollier requested review from a team, durandom and gabemontero as code owners July 3, 2026 15:45
@sonarqubecloud

sonarqubecloud Bot commented Jul 3, 2026

Copy link
Copy Markdown

@rhdh-qodo-merge

Copy link
Copy Markdown

PR Summary by Qodo

Enable fullsend auto-review for ai-integrations workspace

⚙️ Configuration changes 🕐 Less than 5 minutes

Grey Divider

AI Description

• Expand fullsend review auto-trigger to include the ai-integrations workspace.
• Update workflow path filters so PRs touching ai-integrations route to agent review.
High-Level Assessment

This is the simplest and most direct way to enable fullsend for the ai-integrations workspace: extend the existing pull_request.paths filter. Considered using a shared variable/list of workspace paths or broader globbing, but that would add indirection without clear benefit for a single additional workspace.

Files changed (1) +2 / -1

Other (1) +2 / -1
fullsend.yamlTrigger fullsend review workflow for ai-integrations PR changes +2/-1

Trigger fullsend review workflow for ai-integrations PR changes

• Updates the workflow documentation comment and extends the pull_request path filters to include workspaces/ai-integrations/**, enabling review auto-triggers for that workspace.

.github/workflows/fullsend.yaml

@rhdh-qodo-merge

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

Context used
✅ Compliance rules (platform): 11 rules

Grey Divider


Remediation recommended

1. Stale fullsend scope docs 🐞 Bug ⚙ Maintainability
Description
docs/fullsend.md still describes the Review agent auto-trigger as being scoped only to
workspaces/scorecard/**, but the workflow now also auto-triggers for workspaces/boost/** and
workspaces/ai-integrations/**. This mismatch can confuse contributors about when fullsend will run
and how to expand the scope.
Code

.github/workflows/fullsend.yaml[34]

+      - "workspaces/ai-integrations/**"
Relevance

⭐⭐⭐ High

Team often fixes doc/behavior mismatches (accepted in PR #2647; workflow comment alignment in PR
#2763).

PR-#2647
PR-#2763
PR-#3256

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The workflow configuration shows auto-trigger paths include boost, scorecard, and
ai-integrations, while the docs explicitly claim auto-trigger is for workspaces/scorecard/** and
describe that as the paths filter.

.github/workflows/fullsend.yaml[24-36]
docs/fullsend.md[11-37]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`docs/fullsend.md` documents the Review agent as only auto-triggering for `workspaces/scorecard/**`, but `.github/workflows/fullsend.yaml` is configured to auto-trigger on additional workspaces (including the newly-added `workspaces/ai-integrations/**`). This creates incorrect internal documentation.

## Issue Context
The workflow’s `pull_request_target.paths` filter is the source of truth for which workspaces auto-trigger the review agent.

## Fix Focus Areas
- docs/fullsend.md[11-37]
- .github/workflows/fullsend.yaml[24-36]

## Suggested fix
- Update `docs/fullsend.md` to list the current auto-trigger paths (boost, scorecard, ai-integrations) and remove/adjust any statements implying only scorecard is covered.
- Optionally reference the workflow file as the canonical place to check/update scope.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Qodo Logo

@rhdh-qodo-merge rhdh-qodo-merge Bot added the enhancement New feature or request label Jul 3, 2026
@gabemontero gabemontero merged commit 12b0c0b into redhat-developer:main Jul 4, 2026
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants