You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Learn how CodeRabbit works in a pull request review.
5
+
---
6
+
7
+
# Future Developments
8
+
9
+
We are actively iterating and refining CodeRabbit, and this is a sneak peek into the upcoming milestones and releases. We are focused on making the Applied AI review better than the median manual review. In addition to that, we are looking at a holistic user experience with various integrations and types of reviews.
10
+
11
+
## Applied AI Improvements
12
+
13
+
We are actively trying to make the application of Generative AI more useful , relevant , meaningful for the coder and reviewer journey. Our immediate focus is
14
+
15
+
### Accuracy and Conciseness Enhancements
16
+
17
+
- Refining knowledge base context understanding
18
+
- Implementing advanced summarization techniques
19
+
- Implementing a knowledge base feature library
20
+
21
+
### Learning Refinements
22
+
23
+
- We have made significant improvement of the learning Enhancing reinforcement learning based on the user feedback
24
+
25
+
## New Feature Enhancements
26
+
27
+
### Expanded Integrations
28
+
29
+
We are integrating various tool chains to enable coders and reviewers to have a consistent experience irrespective of the tools. The immediate tools would be:
30
+
31
+
-**Circle CI**
32
+
-**Jenkins**
33
+
34
+
### Communication Tool Integrations
35
+
36
+
Communication and the user experience of review via various communication tools are going to be key. We will start with integrations to Slack and Microsoft Teams and will be diving into the design engineering of these flows further:
37
+
38
+
-**Slack**: Real-time notifications and interactive discussions
39
+
-**Microsoft Teams**: Code review conversations within Microsoft ecosystem
40
+
41
+
### Enhanced Review Capabilities
42
+
43
+
These are additional capabilities that can also be reviewed in the same PR to accelerate the coder and reviewer journey. This includes pipeline failure analysis and resolution, as well as vulnerability assessment.
44
+
45
+
#### Pipeline Failure Analysis
46
+
47
+
- Automated analysis of CI/CD pipeline failures
48
+
- AI-driven suggestions for resolving issues
49
+
- Historical tracking of pipeline performance
50
+
51
+
### Finishing Touches
52
+
53
+
Finishing touches are about experience that often take developers time away from what they like doing best - coding. But adding finishing touches is crucial and should follow the ontology and taxonomy. We will start by looking into Docstring and expand to various areas to solve pain points for coders and reviewers.
54
+
55
+
#### 1. DocString Review
56
+
57
+
- Automated checks for docstring presence and quality
58
+
- AI-powered suggestions for improving documentation
59
+
- Resolving Doc-string conflicts in a following PR
60
+
61
+
> Disclaimer: any product roadmap features mentioned below are only meant to outline
62
+
> our general product direction. This documentation is for informational purposes
63
+
> only and may not be incorporated into any contract.
All CodeRabbit users have access to the [CodeRabbit Discord Server](http://discord.gg/coderabbit), where you can ask questions or see what others are doing with CodeRabbit. You will find CodeRabbit users and members of the CodeRabbit team actively engaged.
15
14
16
15
## Support Tickets
17
16
18
-
To get assistance from our support team, open a ticket using the help icon on
19
-
the CodeRabbit UI:
17
+
:::tip
18
+
For assistance from our support team, click the help icon located in the bottom right corner of the [CodeRabbit UI](https://app.coderabbit.ai/login). This will open a chat window where you can submit your support ticket.
19
+
:::
20
+
21
+
Complete the support ticket by providing your name, email, a description of your issue, and attaching any necessary files. If you are reporting a bug, please provide the GitHub or GitLab organization name.
22
+
23
+
24
+
25
+
26
+
27
+
:::note
28
+
If you are a paying user and cannot access the support ticket form in the CodeRabbit UI for some reason, you can contact CodeRabbit support at the following email address: [email protected].
29
+
:::
30
+
31
+
## Customer Responsibilities
20
32
21
-
Complete the support ticket by providing your name, email, a description of your
22
-
issue, and attaching any necessary files. If you are reporting a bug, please
23
-
provide the GitHub or GitLab organization name.
33
+
> To ensure efficient resolution of issues, customers are expected to
24
34
25
-
26
-
35
+
1. Provide detailed information about the issue.
36
+
2. Cooperate with the Support team during troubleshooting.
37
+
3. Utilize available self-service resources/docs for basic inquiries.
27
38
28
-
## Email Support
39
+
## Etiquette
40
+
Regardless of the method or location through which CodeRabbit provides Support, communication should be professional and respectful. Any communication that is deemed objectionable by CodeRabbit staff is not tolerated. This includes but is not limited to any communication that is abusive or contains profane language.
0 commit comments