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

Added documentation for immediate feedback #8523

Merged
merged 2 commits into from
Oct 11, 2024

Conversation

bsekachev
Copy link
Member

@bsekachev bsekachev commented Oct 9, 2024

Motivation and context

How has this been tested?

Checklist

  • I submit my changes into the develop branch
  • I have created a changelog fragment
  • I have updated the documentation accordingly
  • I have added tests to cover my changes
  • I have linked related issues (see GitHub docs)
  • I have increased versions of npm packages if it is necessary
    (cvat-canvas,
    cvat-core,
    cvat-data and
    cvat-ui)

License

  • I submit my code changes under the same MIT License that covers the project.
    Feel free to contact the maintainers if that's a concern.

Summary by CodeRabbit

  • New Features

    • Introduced immediate feedback for annotators, providing performance scores after job completion.
    • Added the ability for annotators to re-annotate jobs based on feedback.
    • Configurable settings for feedback quality on the quality settings page.
  • Documentation

    • New documentation created for immediate feedback, outlining usage, settings, and requirements.

Copy link
Contributor

coderabbitai bot commented Oct 9, 2024

Walkthrough

The changes introduce a new document titled immediate-feedback.md, which details a feature enabling annotators to receive immediate feedback on their performance after job completion. This feedback includes a dialog showing the quality of annotations and allows for re-annotation if the feedback is disputed. The document specifies various settings for this feature, types of feedback, and requirements for its use, ensuring clarity and transparency in the annotation process.

Changes

File Path Change Summary
site/content/en/docs/enterprise/immediate-feedback.md New document created detailing the immediate feedback feature for annotators, including settings, types of feedback, and requirements.

Poem

In the meadow where feedback flows,
Annotations bloom, and knowledge grows.
With scores displayed, both fair and bright,
Re-annotate, adjust, and get it right!
A hop of joy for tasks well done,
Immediate feedback—let's have some fun! 🐇✨


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>, please review it.
    • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @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.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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
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

🧹 Outside diff range and nitpick comments (3)
site/content/en/docs/enterprise/immediate-feedback.md (3)

15-18: Consider adding brief descriptions for each setting.

While the section provides a good overview of where to find the settings, it might be helpful to briefly describe what each setting (Target metric, Target metric threshold, Max validations per job) does. This would give users a better understanding of how these settings affect the immediate feedback feature.


31-38: LGTM: Informative notes section with a suggestion for improvement.

The notes section provides valuable information about the feature's behavior, including timeout, availability limitations, and special cases for staff members and job assignees. This information is crucial for users to understand the feature's limitations and exceptions.

Consider adding a brief explanation of why the 20-second timeout exists and what happens if the timeout is reached. This could help users better understand and work with this limitation.


47-48: Remove extra newlines at the end of the file.

There are unnecessary blank lines at the end of the file. Consider removing these extra newlines to maintain a clean and consistent document structure.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 5f27977 and 4541ba8.

⛔ Files ignored due to path filters (4)
  • site/content/en/images/immediate-feedback-accept.png is excluded by !**/*.png
  • site/content/en/images/immediate-feedback-final-reject.png is excluded by !**/*.png
  • site/content/en/images/immediate-feedback-quality-settings.png is excluded by !**/*.png
  • site/content/en/images/immediate-feedback-reject.png is excluded by !**/*.png
📒 Files selected for processing (1)
  • site/content/en/docs/enterprise/immediate-feedback.md (1 hunks)
🧰 Additional context used
🔇 Additional comments (3)
site/content/en/docs/enterprise/immediate-feedback.md (3)

1-14: LGTM: Front matter and introduction are well-structured and informative.

The metadata and introduction effectively set the context for the "Immediate job feedback" feature. The content is clear, concise, and provides a good overview of the feature's functionality.


20-29: LGTM: Clear explanation of feedback types with visual aids.

This section effectively describes the three types of feedback available to annotators. The inclusion of images for each feedback type enhances the explanation and provides valuable visual context for users.


40-46: LGTM: Clear and concise requirements section.

The requirements for using the immediate feedback feature are well-defined and easy to understand. This section provides users with a clear checklist of conditions that must be met for the feature to be available and functional.

Copy link

@bsekachev bsekachev merged commit 8b8cce1 into develop Oct 11, 2024
15 checks passed
@bsekachev bsekachev deleted the bs/immediate_feedback_docs branch October 24, 2024 05:15
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.

2 participants