Conversation
E2E tests did not runE2E tests run automatically for org/repo members and collaborators on pull requests. For other contributors, a maintainer must add the See E2E testing guide for details. |
1 similar comment
E2E tests did not runE2E tests run automatically for org/repo members and collaborators on pull requests. For other contributors, a maintainer must add the See E2E testing guide for details. |
PR Summary by QodoBump QualityFlow pin to restore CI execution
AI Description
High-Level Assessment
Files changed (1)
|
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)
Great, no issues found!Qodo reviewed your code and found no material issues that require reviewTip of the day💡 Did you know, you can ask Qodo to dismiss a finding you disagree with, with your reason on record |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
QualityFlow added a skip-ci marker to every commit it pushed, which suppressed CI on the PR head, and it committed its outputs/ working directory instead of integrating generated tests into the repo's test suite. Both are fixed upstream in redhat-community-ai-tools/qualityflow-fullsend#2 and redhat-community-ai-tools/qualityflow-fullsend#3. Bump the pinned harness SHA from f6311b4 to 572ba47. harness/qualityflow.yaml is byte-identical, so the sha256 integrity hash is unchanged. Signed-off-by: guy oron <goron@redhat.com>
3a691c0 to
91bbf96
Compare
What
Bump the pinned QualityFlow harness SHA in
.fullsend/config.yamlfromf6311b4to572ba47.Why
Picks up two QualityFlow fixes that change what lands on PRs here:
outputs/is never committed (review on fix: gitignore outputs/ so custom-agent artifacts don't land in PR history #6311).Safety
harness/qualityflow.yamlis byte-identical at both SHAs, so the#sha256=integrity hash is unchanged (verified against the raw URL).f6311b4..572ba47contains only those two PRs: agent prompts underqualityflow/agents/and qualityflow-fullsend's own workflow.