Files

T

History

cdesouza-chromium a7e89eb465 [brockit] Adding drop! command for B🚀 (#37057 )

This command is a sibling to `reassign!`, in the sense that it also
creates a commit with a subcommand tag to guide a rebase event. In this
case though, the `drop!` indicates that a target commit is supposed to
be dropped during rebase.

Similar to `ressign!` handling, this type of pin can only be processed
with `--squash-minor-bumps`, and the target commit cannot be another
pinned commit.

This change is being implemented for rebase v2 only.

Bug: https://github.com/brave/brave-browser/issues/56150

2026-06-07 00:45:18 +01:00

alias

[git-cr] Adding git cr commit --fixup=reassign:hash (#37056 )

2026-06-06 23:19:07 +01:00

iwyu

[docs] Format README.md (#36844 )

2026-06-01 16:00:04 +01:00

test

[mac][brockit] Fix repository_test.py temp path failures (#36503 )

2026-05-18 10:15:17 +01:00

toolchains

[toolchain][brockit] Fixing Xcode toolchain update command (#37058 )

2026-06-07 00:42:33 +01:00

.vpython3

[plaster] Introducing a 🩹 YAML frontend (#36651 )

2026-05-22 15:20:51 +01:00

brockit_test.py

[brockit] Adding drop! command for B🚀 (#37057 )

2026-06-07 00:45:18 +01:00

brockit.py

[brockit] Adding drop! command for B🚀 (#37057 )

2026-06-07 00:45:18 +01:00

fake_chromium_repo_test.py

…

find_rebase_commits.py

…

gen_rust_toolchain_integration_test.py

[brockit] Kick out Rust/WASM CI jobs (#36903 )

2026-06-01 22:50:42 +01:00

gen_rust_toolchain_test.py

[brockit] Kick out Rust/WASM CI jobs (#36903 )

2026-06-01 22:50:42 +01:00

git_status_test.py

[brockit] Make Repository.py paths relative (#36307 )

2026-05-11 10:15:00 +01:00

git_status.py

[brockit] Fix git_status trimming issue (#35908 )

2026-04-27 10:29:03 +01:00

patchfile_test.py

[brockit] Make Repository.py paths relative (#36307 )

2026-05-11 10:15:00 +01:00

patchfile.py

[plaster] Introducing a 🩹 YAML frontend (#36651 )

2026-05-22 15:20:51 +01:00

plaster_test.py

[plaster] Introducing a 🩹 YAML frontend (#36651 )

2026-05-22 15:20:51 +01:00

plaster.py

[plaster] Introducing a 🩹 YAML frontend (#36651 )

2026-05-22 15:20:51 +01:00

post_presubmit.py

[toolchain] Checkout the tag manually on the rust WASM builder (#36615 )

2026-05-21 18:00:40 +01:00

PRESUBMIT.py

Moving git-cr code under alias/ (#36154 )

2026-05-05 15:31:03 +01:00

prune_test_filters_test.py

Script for pruning obsolete upstream test filters (#35339 )

2026-04-14 18:55:33 -04:00

prune_test_filters.py

[brockit] Fixing dos-and-donts violations (#36416 )

2026-05-13 17:04:36 +01:00

python_dos_and_donts.md

[brockit] Adding a section about classes to dos and donts (#36671 )

2026-05-24 00:46:42 +01:00

README.md

[docs] Format README.md (#36844 )

2026-06-01 16:00:04 +01:00

rebase_test.py

[brockit] Test coverage for Rebase (#36315 )

2026-05-11 12:10:59 +01:00

rebase_v2_test.py

[brockit] Adding drop! command for B🚀 (#37057 )

2026-06-07 00:45:18 +01:00

rebase_v2.py

[brockit] Adding drop! command for B🚀 (#37057 )

2026-06-07 00:45:18 +01:00

repository_test.py

[toolchain][brockit] Adding update-xcode-toolchain (#36514 )

2026-05-19 17:44:55 +01:00

repository.py

[toolchain][brockit] Adding update-xcode-toolchain (#36514 )

2026-05-19 17:44:55 +01:00

terminal.py

[brockit] Kick out Rust/WASM CI jobs (#36903 )

2026-06-01 22:50:42 +01:00

update_rust_wasm_toolchain_test.py

[brockit] Add update-rust-wasm-toolchain command (#37021 )

2026-06-05 14:35:16 +01:00

update_xcode_toolchain_test.py

[toolchain][brockit] Fixing Xcode toolchain update command (#37058 )

2026-06-07 00:42:33 +01:00

versioning_test.py

[brockit] Make Repository.py paths relative (#36307 )

2026-05-11 10:15:00 +01:00

versioning.py

[brockit] Adding labels for fetching the latest tag from git (#35926 )

2026-04-26 23:45:46 +01:00

vpython_utils.py

[brockit] Tooling path further restructure for relative paths (#36322 )

2026-05-11 17:27:13 +01:00

vscode_test.py

[brockit] Simplify Patchfile determination of underlying source (#36101 )

2026-05-01 21:44:00 +01:00

vscode.py

[brockit] Simplify Patchfile determination of underlying source (#36101 )

2026-05-01 21:44:00 +01:00

README.md

`tools/cr`

Python tooling maintained by the Chromium Rebase team to support upgrading brave-core to new Chromium versions and to manage the patches and shadow files that live on top of upstream.

All scripts here are intended to run via vpython3; the .vpython3 spec in this directory pulls in rich, requests, and the other wheels they need. Most scripts accept --verbose to switch logging to DEBUG.

Important

Before adding or editing Python in this directory, read Python dos and donts.

Entry points

These are the user-facing scripts in this directory:

🚀Brockit — End-to-end rebase orchestration. Updates the Chromium version, regenerates patches and strings, and walks the rebase forward.
🩹Plaster — Applies and regenerates "plaster" files: semantic patches against upstream Chromium sources.
post_presubmit.py — Posts and refreshes GitHub PR comments from a npm run presubmit JSON dump.
find_rebase_commits.py — Resolves a Chromium rebase tag (e.g. cr148) to an oldest..newest git commit range.
prune_test_filters.py — Detects and (optionally) removes obsolete entries from the current platform's test-filter files.

Library modules

Shared abstractions used by the entry points and tests:

repository.py — Repository instances (repository.brave, repository.chromium) for paths and for running git commands at any repo.
terminal.py — Rich console, baseline logging config, and subprocess utilities.
vpython_utils.py — Provides vpython3 path.
patchfile.py — Patch file abstraction handling patches that failed to apply.
git_status.py — Parser for git status --porcelain output.
versioning.py — Chromium version number parsing.
vscode.py — IPC for opening files in VS Code in the integrated terminal.

Subdirectories

alias/ — git cr git-alias subcommands (commit, mv, follow-renames, ...). See alias/README.md.
test/ — Shared test fixtures, including FakeChromiumRepo.
toolchain/ — Scripts to build platform-specific toolchains when rebasing Chromium.

Tests

Every module of interest ships a *_test.py next to it. Tests should always have a vpython3 shebang line, and +x mode, so they can be run as their own utilities from the repo root.

Tests should keep mock use to a minimum. Make sure to always use FakeChromiumRepo to provide a test enviroment. Scripts tested with FakeChromiumRepo should rely always on relative paths derived from Repository.brave.root to permit tests to be run in integration with the repository sandbox provided with FakeChromiumRepo.