docs: state that a renamed file counts at both of its paths

[sileht]

The rename semantics of file-pattern scopes, barrier_files and the files /
added-files / removed-files / modified-files condition attributes were
written down nowhere, so the only way to learn that a rename is treated as a
removal at the source plus an addition at the destination was to try it.

Document the rule where each surface is described, with the git mv example
spelled out attribute by attribute, and note that #files is GitHub's own
changed-file count and so does not equal the length of files on a pull
request containing a rename.

While verifying the rename example against the engine's actual glob matcher, two
things turned out to be wrong on this page and are fixed here too:

• the rename example used git mv api/auth.py web/auth.py, but web/auth.py matches
  none of the frontend patterns (they are .js/.jsx/.ts/.tsx), so it reported
  one scope, not both;
• the multi-language example declared apps/web/**/*.{js,jsx,ts,tsx}. Brace expansion
  is not supported by the matcher, so that pattern matched nothing and the frontend
  scope in that example could never fire. Expanded into one pattern per extension.

Related to MRGFY-8248

[mergify]

Merge Protections

🟢 All 6 merge protections satisfied — ready to merge.

Show 6 satisfied protections

🟢 🤖 Continuous Integration

• all of:
  • check-success = build
  • check-success = lint
  • check-success = test
  • any of:
    • check-success = test-broken-links
    • label = ignore-broken-links
  • any of:
    • check-success=Cloudflare Pages
    • -head-repo-full-name~=^Mergifyio/

🟢 👀 Review Requirements

• any of:
  • #approved-reviews-by >= 2
  • author = dependabot[bot]
  • author = mergify-ci-bot

🟢 Enforce conventional commit

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:

🟢 🔎 Reviews

• #changes-requested-reviews-by = 0
• #review-requested = 0
• #review-threads-unresolved = 0

🟢 📕 PR description

• body ~= (?ms:.{48,})

🟢 🚦 Auto-queue

When all merge protections are satisfied, this pull request will be queued automatically.

[Copilot]

Pull request overview

Documents how Mergify treats renamed files when evaluating file-pattern scopes, barrier_files, and condition attributes like files / added-files / removed-files / modified-files, including the note that GitHub’s #files count differs from Mergify’s files list length on renames.

Changes:

• Add an “important behavior” note that renames are matched at both the source and destination paths for scopes and barrier_files.
• Add a conditions reference section explaining rename semantics across files, added-files, removed-files, modified-files, and #files.
• Reinforce barrier behavior in the scopes overview doc.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
src/content/docs/merge-queue/scopes/file-patterns.mdx	Adds a section explaining that renamed files are matched at both paths for scope detection and barrier_files.
src/content/docs/merge-queue/scopes.mdx	Adds a concise note that renames match both paths for barrier_files behavior.
src/content/docs/configuration/conditions.mdx	Adds a “Renamed Files” subsection documenting rename semantics for file-related condition attributes and #files.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[sileht]

Revision history

#	Type	Changes	Reason	Date
1	initial	224b54a		2026-07-30 09:24 UTC
2	content	224b54a → 4c0ef93		2026-07-30 09:24 UTC

Pull request has been modified.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-07-30 09:45 UTC · Rule: default · triggered by merge protections
• ✅ Checks passed · on draft merge queue: checking main (a1f510a) and #12255 together #12267
• ✅ Merged — 2026-07-30 09:48 UTC · at 4c0ef93a026539fbee59142df2e2757e47f4bf62 · squash

This pull request spent 2 minutes 49 seconds in the queue, including 2 minutes 15 seconds running CI.

Required conditions to merge

• github-review-approved [🛡 GitHub repository ruleset rule Require pull request for default branch]
  • docs: state that a renamed file counts at both of its paths #12255
• schedule=Mon-Fri 09:00-17:30[Europe/Paris]
• all of [🛡 Merge Protections rule Enforce conventional commit]:
  • title ~= ^(fix|feat|internal|docs|style|refactor|perf|test|build|ci|chore|revert|ui)(?:\(.+\))?!?:
    • docs: state that a renamed file counts at both of its paths #12255
• all of [🛡 Merge Protections rule 👀 Review Requirements]:
  • any of:
    • #approved-reviews-by >= 2
      • docs: state that a renamed file counts at both of its paths #12255
    • author = dependabot[bot]
      • docs: state that a renamed file counts at both of its paths #12255
    • author = mergify-ci-bot
      • docs: state that a renamed file counts at both of its paths #12255
• all of [🛡 Merge Protections rule 📕 PR description]:
  • body ~= (?ms:.{48,})
    • docs: state that a renamed file counts at both of its paths #12255
• all of [🛡 Merge Protections rule 🔎 Reviews]:
  • #changes-requested-reviews-by = 0
    • docs: state that a renamed file counts at both of its paths #12255
  • #review-requested = 0
    • docs: state that a renamed file counts at both of its paths #12255
  • #review-threads-unresolved = 0
    • docs: state that a renamed file counts at both of its paths #12255
• all of [🛡 Merge Protections rule 🤖 Continuous Integration]:
  • all of:
    • check-success = build
    • check-success = lint
    • check-success = test
    • any of:
      • check-success = test-broken-links
      • label = ignore-broken-links
        • docs: state that a renamed file counts at both of its paths #12255
    • any of:
      • check-success=Cloudflare Pages
      • -head-repo-full-name~=^Mergifyio/
        • docs: state that a renamed file counts at both of its paths #12255