Conversation
Bump version to 0.9.0 Signed-off-by: Petr "Stone" Hracek <phracek@redhat.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #227 +/- ##
===========================================
+ Coverage 35.50% 50.69% +15.18%
===========================================
Files 7 7
Lines 1011 1006 -5
===========================================
+ Hits 359 510 +151
+ Misses 652 496 -156
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 17 minutes and 12 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughUpdated upstream daily-tests image version from Changes
Sequence Diagram(s)(omitted) Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
Makefile (1)
10-10: Consider centralizing the image tag to avoid multi-file drift.Line 10 hardcodes
0.9.0; the same value is duplicated across workflow/Dockerfile/Makefile. Defining one variable in the Makefile (and reusing it where possible) will reduce future mismatch risk.Proposed refactor
+UPSTREAM_DAILY_TESTS_TAG ?= 0.9.0 + build_images: - podman build -t quay.io/sclorg/upstream-daily-tests:0.9.0 -f Dockerfile.daily-tests . + podman build -t quay.io/sclorg/upstream-daily-tests:$(UPSTREAM_DAILY_TESTS_TAG) -f Dockerfile.daily-tests .🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@Makefile` at line 10, Centralize the image tag by adding a variable (e.g., DAILY_TESTS_TAG or IMAGE_TAG) in the Makefile and replace the hardcoded literal in the podman build command (the line invoking "podman build -t quay.io/sclorg/upstream-daily-tests:0.9.0 -f Dockerfile.daily-tests .") with a reference to that variable; update any other project files that currently duplicate the tag to read from this Makefile variable (or a single source such as an exported env file) so the tag is maintained in one place and future changes won’t drift across Dockerfile/workflow/Makefile.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@daily-tests/daily_tests/daily_nightly_tests_report.py`:
- Around line 190-191: Remove the unconditional override of self.send_email and
instead parse the environment variable properly: read SEND_EMAIL as a string
(e.g., os.getenv("SEND_EMAIL", "False") or similar), normalize it (strip and
lower) and set self.send_email to True only if the value is one of common truthy
tokens ("1","true","yes","on"); update the assignment where self.send_email is
currently set (replace the two lines referencing self.send_email in the
constructor or initializer) so the env var controls email sending with a safe
default of False.
---
Nitpick comments:
In `@Makefile`:
- Line 10: Centralize the image tag by adding a variable (e.g., DAILY_TESTS_TAG
or IMAGE_TAG) in the Makefile and replace the hardcoded literal in the podman
build command (the line invoking "podman build -t
quay.io/sclorg/upstream-daily-tests:0.9.0 -f Dockerfile.daily-tests .") with a
reference to that variable; update any other project files that currently
duplicate the tag to read from this Makefile variable (or a single source such
as an exported env file) so the tag is maintained in one place and future
changes won’t drift across Dockerfile/workflow/Makefile.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: f3313cb5-024c-4673-94be-374afac02c38
📒 Files selected for processing (4)
.github/workflows/build-and-push.ymlDockerfile.daily-testsMakefiledaily-tests/daily_tests/daily_nightly_tests_report.py
Signed-off-by: Petr "Stone" Hracek <phracek@redhat.com>
Signed-off-by: Petr "Stone" Hracek <phracek@redhat.com>
Bump version to 0.9.0
Summary by CodeRabbit
Chores
Refactor