docs: document unified merge queue bot_account#12140
Open
jd wants to merge 1 commit into
Open
Conversation
Contributor
Merge Protections🔴 1 of 7 protections blocking · waiting on ⛓️ dependency
🔴 ⛓️ Depends-On RequirementsWaiting for
This rule is failing.Requirement based on the presence of
Show 6 satisfied protections🟢 🤖 Continuous Integration
🟢 👀 Review Requirements
🟢 Enforce conventional commitMake sure that we follow https://www.conventionalcommits.org/en/v1.0.0/
🟢 🔎 Reviews
🟢 📕 PR description
🟢 🚦 Auto-queueWhen all merge protections are satisfied, this pull request will be queued automatically. |
There was a problem hiding this comment.
Pull request overview
Updates the Mergify docs’ “Bot account” data type reference to reflect the merge queue configuration key rename from draft_bot_account to bot_account, while keeping the former name discoverable for readers migrating existing configs.
Changes:
- Replaces the merge queue key reference
draft_bot_accountwithbot_account. - Adds a parenthetical note to indicate the former key name (
draft_bot_account) for migration recognition.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
jd
marked this pull request as ready for review
July 17, 2026 15:01
jd
changed the title
jd
force-pushed
the
devs/jd/jd/bot-account-docs/rename-queue-key-draft-bot-account-bot-account--4e705e37
branch
from
July 17, 2026 15:13
8a88b6d to
71064a2
Compare
Member
Author
Revision history
|
jd
marked this pull request as draft
July 17, 2026 15:16
jd
commented
Jul 17, 2026
Mergify unifies the three per-operation merge-queue bot accounts — `draft_bot_account`, `merge_bot_account`, and `update_bot_account` — into a single `bot_account` key (Mergifyio/monorepo#37097). This drops per-operation account granularity: one account now performs every queue operation (creating draft pull requests, updating branches, merging). Update the docs to match: - configuration/data-types.mdx — rewrite the "Bot account" section to describe the single unified key and add a dateless deprecation-alias note: the three old keys are deprecated aliases that map to `bot_account`, and on conflicting values a defined precedence wins (`merge_bot_account` > `update_bot_account` > `draft_bot_account`) with a warning. - merge-queue/merge-strategies.mdx, merge-queue/batches.mdx — replace the remaining `update_bot_account` example/prose references with `bot_account`. Left untouched on purpose: the auto-generated schemas (public/mergify-configuration-schema.json, public/api-schemas.json) are regenerated externally from the monorepo, and the historical changelog entries record their original features. The public changelog is synced from the monorepo, so the unification announcement lands there, not in this repo. Depends-On: Mergifyio/monorepo#37097 Change-Id: I4e705e37b673210b1d5f4d04a0411d2c8e8c6f94
jd
force-pushed
the
devs/jd/jd/bot-account-docs/rename-queue-key-draft-bot-account-bot-account--4e705e37
branch
from
July 17, 2026 16:22
71064a2 to
1d1db24
Compare
jd
marked this pull request as ready for review
July 20, 2026 17:24
JulianMaurin
approved these changes
Jul 20, 2026
kozlek
approved these changes
Jul 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Mergify unifies the three per-operation merge-queue bot accounts —
draft_bot_account,merge_bot_account, andupdate_bot_account— into asingle
bot_accountkey (Mergifyio/monorepo#37097). This drops per-operationaccount granularity: one account now performs every queue operation (creating
draft pull requests, updating branches, merging).
Update the docs to match:
the single unified key and add a dateless deprecation-alias note: the three
old keys are deprecated aliases that map to
bot_account, and on conflictingvalues a defined precedence wins (
merge_bot_account>update_bot_account>draft_bot_account) with a warning.remaining
update_bot_accountexample/prose references withbot_account.Left untouched on purpose: the auto-generated schemas
(public/mergify-configuration-schema.json, public/api-schemas.json) are
regenerated externally from the monorepo, and the historical changelog entries
record their original features. The public changelog is synced from the
monorepo, so the unification announcement lands there, not in this repo.
Depends-On: https://github.com/Mergifyio/monorepo/pull/37097