docs(rulesets): clarify auto-merge bypass behavior

[aniruddhaadak80]

Why:

Closes: #45265

The ruleset creation guidance explains how to grant bypass permissions but does not explain that a bypass used for a pull request rule is not currently honored when auto-merge completes the merge. This can leave automation blocked even though the bypass actor is listed and eligible for a direct merge.

What's being changed (if available, include any code snippets, screenshots, or gifs):

• Add a note beside the bypass-permission setup explaining the auto-merge limitation.
• Tell readers who rely on a bypass actor to use a direct merge request instead of enabling auto-merge.
• Keep the change on the ruleset creation page so it does not overlap with the separate merge-queue branch creation documentation.
• Evidence: issue Rulesets docs don't disclose that bypass_actors is not honored by auto-merge completion #45265 includes a reproducible comparison between a blocked auto-merge run and an immediately successful direct merge request using the same bypass actor.
• Testing:
  • npm run build - passed.
  • npm run lint-content -- --paths content/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository.md - passed with no errors.
  • npm test -- src/content-render/tests/render-changed-and-deleted-files.ts - 2 tests passed.
  • git diff --check - passed.

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/creating-rulesets-for-a-repository.md	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18 3.17	fpt ghec ghes@ 3.22 3.21 3.20 3.19 3.18 3.17

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[subatoi]

I'm going to close this out—we haven't marked this as ready for community contributions yet, and are yet to make a determination about the best way to tackle the problem. Apologies that this won't be the outcome you were hoping for