-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Issue management docs, auto-close and triage comment workflow (Lombiq Technologies: OCORE-161) #15820
Conversation
Note Reviews PausedUse the following commands to manage reviews:
WalkthroughThe changes primarily focus on enhancing issue and pull request management in the OrchardCore project. This includes updates to GitHub workflows and templates to improve automation, communication, and clarity in handling issues and PRs. Additionally, documentation has been expanded and updated to guide contributors more effectively. Changes
Assessment against linked issues
Possibly related issues
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is how this looks like: https://github.com/Lombiq/OCORE-161-workflows-test/issues/3.
- A [milestone](https://github.com/OrchardCMS/OrchardCore/milestones) is assigned to it, see below. This means we think your issue is definitely worth addressing, thank you! | ||
- We close it. If your issue is a duplicate of an earlier one, is a report about a bug that's already fixed, or something that we don't think is a good match for Orchard Core, we'll close it with an explanation. This is not against you, it's just that we can't address all issues. Please don't hesitate to open new issues for other matters. | ||
|
||
## Issue milestones |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have these P0-P3 labels, I assume P0 meaning the most important and P3 the least important issues. A small fraction of the issues are marked as such, though. I'd just remove these and only use milestones. OK to remove them?
@@ -1,4 +1,4 @@ | |||
blank_issues_enabled: true | |||
blank_issues_enabled: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are almost 500 issues without labels, because we didn't enforce the very rudimentary task of making the author select if their issue is a bug or feature request. This makes managing those issues a lot harder.
I'd actually also enforce the templates too (like this one). Currently, you can just remove the template and write into the issue description whatever. This requires the one replying to the issue ask the same questions.
What do you think?
revisit any time soon or should we close? Pleaes comment if you'd like to pick it up and remove the | ||
"stale" label. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The "stale" label is actually removed automatically.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
Out of diff range and nitpick comments (1)
src/docs/guides/contributing/contributing-code.md (1)
29-29
: Consider removing trailing spaces for cleaner Markdown formatting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 3
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 3
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 3
@coderabbitai stop |
Tip For best results, initiate chat on the files or code changes. @Piedone, I've stopped all actions as requested. If there's anything else you need, feel free to let me know. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
@coderabbitai pause |
This pull request has merge conflicts. Please resolve those before requesting a review. |
# Conflicts: # mkdocs.yml
This pull request has merge conflicts. Please resolve those before requesting a review. |
# Conflicts: # .github/workflows/close_stale_prs.yml
Can I get a review here from one of you @hishamco @MikeAlhayek @sebastienros? This has been sitting here for weeks. Also see the comments I've added above. |
Co-authored-by: Sébastien Ros <[email protected]>
@hishamco @MikeAlhayek @sebastienros If you asked the author something and the issue should be closed if they don't reply, now you can add the |
Fixes #15034.