fix: getAppSetStatus incorrectly treats ApplicationSetUpToDate=True as Error - #284
Conversation
…s Error Signed-off-by: Atif Ali <atali@redhat.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughSummary by CodeRabbit
WalkthroughThe ApplicationSet status evaluation now checks ChangesApplicationSet status evaluation
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This localized status-handling change has no actionable merge-blocking risk remaining and is merge-ready after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #284 +/- ##
==========================================
+ Coverage 11.30% 12.40% +1.10%
==========================================
Files 169 171 +2
Lines 6679 6835 +156
Branches 2235 2319 +84
==========================================
+ Hits 755 848 +93
- Misses 5923 5986 +63
Partials 1 1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
/lgtm |
See: GITOPS-11094