Skip to content

Unit test gen docs #398

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

Merged
merged 9 commits into from
Jun 13, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
lets not lmao
  • Loading branch information
Howon Lee committed Jun 12, 2025
commit f6ac90079c6b53efba047655bb3593d0da2c6a56
4 changes: 0 additions & 4 deletions docs/finishing-touches/unit-test-generation.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,10 +29,6 @@ Once sent, CodeRabbit will perform the following actions:
- Unit tests will be generated for the PR, in a separate PR, in the same PR in a new commit, or in a comment to copy-paste, depending on your choice
- If (and only if) you choose to generate the unit tests in a separate PR, CodeRabbit will examine your GitHub checks (build steps and tests and such) and adjust the PR to deal with build failures, test failures and similar.

Here's an example of what a pull request may look like:

![Unit Tests PR](/img/finishing-touches/unit-tests-pull-request.png)

## Path Instructions

You can customize the generated unit tests by providing instructions based on file paths in your `.coderabbit.yaml`. The `path` is a [minimatch](https://github.com/isaacs/minimatch) pattern.
Expand Down