add bough to mutation testing section

[CodeEnPlace]

Summary by Sourcery

Documentation:

• Document the bough polyglot incremental mutation tester in the mutation testing tools section of the README.

[semanticdiff-com]

Review changes with  

[qodo-code-review]

Review Summary by Qodo

Add bough to mutation testing section

📝 Documentation

Walkthroughs

Description

• Add bough mutation testing tool to resources list
• Bough is a polyglot incremental mutation tester

Diagram

flowchart LR
  README["README.md"] -- "Add bough link" --> MutationTools["Mutation Testing Tools List"]

Loading

File Changes

1. README.md 📝 Documentation +1/-0

Add bough mutation testing tool reference

• Added bough link to mutation testing section
• Bough described as polyglot incremental mutation tester
• Inserted between xmutant.py and Object Factories sections

README.md

---

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds the Bough mutation testing tool to the README’s mutation testing tools list.

File-Level Changes

Change	Details	Files
Extend the mutation testing tools list in the README with an entry for the Bough incremental mutation tester.	Add a new bullet for Bough with its GitHub URL to the mutation testing section Provide a short description indicating Bough is a polyglot incremental mutation tester	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1)   📘 Rule violations (0)   📎 Requirement gaps (0)   🎨 UX Issues (0)

🐞\ ⚙ Maintainability (1)

1. Unsorted list entry 🐞 ⚙

Description

The new 'bough' entry is appended at the end of the 'Mutation Testing' list even though the
surrounding entries are alphabetically ordered. This breaks list consistency and makes the curated
section harder to scan and maintain over time.

Code

README.md[128]

+- [bough](https://github.com/CodeEnPlace/bough) - Bough is a polyglot incremental mutation tester

Evidence

In the 'Mutation Testing' section, existing tools are ordered by name (Cosmic Ray → Mutatest →
Mutmut → MutPy → xmutant.py). The newly added 'bough' (starting with 'b') is placed after
'xmutant.py', which is out of order; other nearby README lists also follow alphabetical ordering,
reinforcing that ordering is intentional.

README.md[121-129]
README.md[91-97]
README.md[99-118]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The newly added `bough` bullet is out of alphabetical order within the `## Mutation Testing` list.

## Issue Context
Other README sections and the existing `Mutation Testing` entries appear alphabetically sorted, so adding an out-of-order item reduces consistency.

## Fix Focus Areas
- README.md[121-129]

## Suggested change
Move the `bough` bullet to its alphabetical position (e.g., before `Cosmic Ray`).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request adds the bough mutation testing tool to the README. The feedback suggests maintaining alphabetical order within the section and refining the description for better conciseness.

[gemini-code-assist]

The "Mutation Testing" section is currently sorted alphabetically. To maintain this consistency, the entry for bough should be moved to the beginning of the list (before Cosmic Ray). Additionally, the description can be made more concise by removing the redundant project name.

Suggested change

	- [bough](https://github.com/CodeEnPlace/bough) - Bough is a polyglot incremental mutation tester
	- [bough](https://github.com/CodeEnPlace/bough) - A polyglot incremental mutation tester

[llamapreview]

Auto Pull Request Review from LlamaPReview

Review Status: Automated Review Skipped

Dear contributor,

Thank you for your Pull Request. LlamaPReview has analyzed your changes and determined that this PR does not require an automated code review.

Analysis Result:

PR only contains documentation changes (1 files)

Technical Context:

Documentation changes typically include:

• Markdown/RST file updates
• API documentation
• Code comments
• README updates
• Documentation in /docs directory
• License and contribution files

We're continuously improving our PR analysis capabilities. Have thoughts on when and how LlamaPReview should perform automated reviews? Share your insights in our GitHub Discussions.

Best regards,
LlamaPReview Team