Skip to content

Conversation

oetr
Copy link
Contributor

@oetr oetr commented Oct 9, 2025

No description provided.

- this example does not use rules_fuzzing
@Copilot Copilot AI review requested due to automatic review settings October 9, 2025 13:32
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR enhances the Bazel documentation section by adding information about JUnit5 integration and improves various descriptions throughout the README. The changes provide clearer guidance for users wanting to use Jazzer with Bazel and JUnit5, while also fixing inconsistencies in examples and improving formatting.

  • Added documentation for using Jazzer with JUnit5 integration in Bazel, including a link to an example project
  • Restructured the Bazel section with clearer subsections for different integration approaches
  • Fixed inconsistencies in class names used in examples and improved general documentation clarity

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

@oetr oetr mentioned this pull request Oct 9, 2025
Co-authored-by: Marcono1234 <Marcono1234@users.noreply.github.com>
Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>
@oetr oetr force-pushed the CIF-1819-bazel-junit-docs branch from 9b22fd3 to bb3d2ff Compare October 9, 2025 14:00
@oetr oetr enabled auto-merge (rebase) October 9, 2025 14:20
Copy link
Contributor

@simonresch simonresch left a comment

Choose a reason for hiding this comment

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

Good follow up. Thanks!

@oetr oetr merged commit f21f209 into main Oct 9, 2025
8 checks passed
@oetr oetr deleted the CIF-1819-bazel-junit-docs branch October 9, 2025 16:49
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