-
-
Notifications
You must be signed in to change notification settings - Fork 114
feat(queue): support consumer lifecycle mgmt for queue & set retry to 1 #931
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 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 |
|
@coderabbitai: Provide a valid title |
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain@zhravan, I'll help you provide a valid title for this PR. Let me first gather information about the changes in this PR. 🏁 Script executed: Length of output: 22416 @zhravan, I've analyzed the PR changes. The current title "Css/enhancements" is completely incorrect - this PR has nothing to do with CSS! The PR actually includes:
Here are my title suggestions following conventional commit format: Recommended: Alternatives: Would you like me to update the PR title using the GitHub CLI? 🏁 Script executed: Length of output: 16 @zhravan, I've confirmed the current title is indeed "Css/enhancements". Which of the suggested titles would you like me to use? Or would you prefer a different title? Once you confirm, I can update the PR title for you immediately. My top recommendation: Just let me know which one you prefer, or provide your own title, and I'll update it! 👍 |
Issue
Link to related issue(s):
Description
Short summary of what this PR changes or introduces.
Scope of Change
Select all applicable areas impacted by this PR:
Screenshot / Video / GIF (if applicable)
Attach or embed screenshots, screen recordings, or GIFs demonstrating the feature or fix.
Related PRs (if any)
Link any related or dependent PRs across repos.
Additional Notes for Reviewers (optional)
Anything reviewers should know before testing or merging (e.g., environment variables, setup steps).
Developer Checklist
To be completed by the developer who raised the PR.
Reviewer Checklist
To be completed by the reviewer before merge.