Added logic to proceed in pipeline when trying to re-run jobs without commit - #1871
Merged
Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughCI workflow updated to conditionally commit and push changes to kustomization.yaml only when staged modifications exist, replacing unconditional git commit/push with a guarded check and informational message when no changes are present. ChangesCI guard for empty commits
Sequence Diagram(s)sequenceDiagram
autonumber
actor Dev as Developer
participant GH as GitHub Actions (CI)
participant Git as Git
Dev->>GH: Push changes
GH->>GH: Build and update kustomization.yaml
GH->>Git: git add kustomization.yaml
alt Changes staged
GH->>Git: git commit -m "Auto-update kustomization.yaml"
GH->>Git: git push
note right of GH: Commit and push proceed
else No staged changes
GH->>GH: Echo "No changes to commit"
note right of GH: Skip commit/push
end
Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 |
Despire
approved these changes
Oct 17, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added logic to allow the pipeline to proceed when re-running jobs without requiring a new commit.
This improves testing speed. If the pipeline failed for a reason unrelated to the code (before the
edit-kustomizationjob) - you had to push an empty commit to restart pipeline.That would re-run the entire pipeline from the beginning, even if most jobs had already passed. Example: https://github.com/berops/claudie/actions/runs/18340633694/attempts/2
If you do not commit new message and re-run pipeline manualy pipeline will fail. Here is example of this: https://github.com/berops/claudie/actions/runs/18340633694/job/52285267386#step:8:20
Adding the if statement in the step
Commit new kustomization.yaml to feature branchcan save over 30 minutes during testing.Summary by CodeRabbit