Ignoring Pull Requests

Not all pull requests are created equal. Some are critical code changes that need a thorough review, while others are automated dependency bumps, release preparations, or minor UI tweaks. Getting automated review comments on these can clutter your workflow and distract from the PRs that truly need attention.

To help you focus on the code that matters most, NeetoBugWatch will now identify and skip reviewing certain pull requests, keeping your process clean and efficient.

How It Works

There are two ways NeetoBugWatch decides to skip a review:

1. Automatic Filtering (Based on PR Title)

2. Manual Ignoring (For One-Off Cases)

PRs We'll Automatically Skip

Based on common development patterns, NeetoBugWatch will now automatically skip PRs whose titles indicate they don't contain new logic to review. This includes:

• Release PRs: Titles starting with Release (e.g., Release 2025-08-12).

• Dependency Updates: Titles starting with Bump (e.g., Bump Rails to 7.1.4).

• Reverted Changes: Titles starting with Revert.

• UI-Only Changes: Titles starting with UI:.

• Testing PRs: Titles containing Playwright or starting with test or testing.

• Automated PRs: Titles from services like Neeto Compliance, neeto-translate, or NeetoDataSync.

You don't need to do anything to enable this - it's now a standard part of our review process.

Ignoring PRs Manually

Sometimes you have a one-off pull request that doesn't need a review, like an experiment or a work-in-progress that isn't ready for feedback.

For any pull request you want NeetoBugWatch to ignore, simply include the following keyword anywhere in the PR's first comment (the description):

neeto-bugwatch-ignore

When the bot sees this keyword, it will gracefully skip the review for that specific PR, no questions asked.