Skip to content
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

Merged
merged 25 commits into from
May 23, 2024

Conversation

Piedone
Copy link
Member

@Piedone Piedone commented Apr 24, 2024

Fixes #15034.

Copy link
Contributor

coderabbitai bot commented Apr 24, 2024

Note

Reviews Paused

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Walkthrough

The 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

File Path Change Summary
.github/ISSUE_TEMPLATE/... Added guidance for issue management in templates
.github/workflows/... Updated workflows to handle stale issues/PRs and add comments on triage
mkdocs.yml, src/docs/guides/contributing/... Updated and added documentation sections on issue management and contributing

Assessment against linked issues

Objective Addressed Explanation
Triage all yet untriaged issues (#15034) It's unclear if all untriaged issues are addressed, but workflows and documentation updates support ongoing triage efforts.
Document issue management and prioritization clearly (#15034)
Automatically add comments when issues are triaged (#15034)
Automatically close issues with no feedback from the author (#15034)
Remove and simplify priority labels to use milestones only (#15034)

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?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

- 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
Copy link
Member Author

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
Copy link
Member Author

@Piedone Piedone Apr 24, 2024

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?

Comment on lines 17 to 18
revisit any time soon or should we close? Pleaes comment if you'd like to pick it up and remove the
"stale" label.
Copy link
Member Author

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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a 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

src/docs/guides/contributing/managing-issues.md Outdated Show resolved Hide resolved
src/docs/guides/contributing/managing-issues.md Outdated Show resolved Hide resolved
Piedone and others added 3 commits April 25, 2024 21:45
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Copy link
Contributor

@coderabbitai coderabbitai bot left a 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

src/docs/guides/contributing/managing-issues.md Outdated Show resolved Hide resolved
src/docs/guides/contributing/managing-issues.md Outdated Show resolved Hide resolved
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Copy link
Contributor

@coderabbitai coderabbitai bot left a 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

src/docs/guides/contributing/managing-issues.md Outdated Show resolved Hide resolved
Copy link
Contributor

@coderabbitai coderabbitai bot left a 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

src/docs/guides/contributing/managing-issues.md Outdated Show resolved Hide resolved
src/docs/guides/contributing/managing-issues.md Outdated Show resolved Hide resolved
src/docs/guides/contributing/managing-issues.md Outdated Show resolved Hide resolved
src/docs/guides/contributing/managing-issues.md Outdated Show resolved Hide resolved
src/docs/guides/contributing/managing-issues.md Outdated Show resolved Hide resolved
Copy link
Contributor

@coderabbitai coderabbitai bot left a 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

src/docs/guides/contributing/managing-issues.md Outdated Show resolved Hide resolved
Copy link
Contributor

@coderabbitai coderabbitai bot left a 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

@Piedone
Copy link
Member Author

Piedone commented Apr 25, 2024

@coderabbitai stop

Copy link
Contributor

coderabbitai bot commented Apr 25, 2024

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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a 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

@Piedone
Copy link
Member Author

Piedone commented Apr 26, 2024

@coderabbitai pause

Copy link
Contributor

This pull request has merge conflicts. Please resolve those before requesting a review.

Copy link
Contributor

This pull request has merge conflicts. Please resolve those before requesting a review.

# Conflicts:
#	.github/workflows/close_stale_prs.yml
@Piedone
Copy link
Member Author

Piedone commented May 17, 2024

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]>
@MikeAlhayek MikeAlhayek merged commit 98bca75 into OrchardCMS:main May 23, 2024
6 checks passed
@Piedone
Copy link
Member Author

Piedone commented May 24, 2024

@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 needs author feedback label. This will automatically mark the issue as stale after 15 days, and then close it after another 7.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Get our issue management game in order
3 participants