This change adds a few tests to cover the code in `Patchfile`. This
doesn't cover all cases to these files, but it is a good start, and it
manages to cover the core operation of applying patches.
A lot of test machinery is being introduced to provide some fake support
ot what normally would be done by checkout framework managed in node.
Resolves https://github.com/brave/brave-browser/issues/45232
* Resolve custom tab activity issue which hides bottom toolbar
* Only show bottom controls when bottom toolbar is enabled
Refactor activity finish
* override finish to make sure of activity closure
* Enable Tab Focus UI
* Backend change to support first time use UI for tab focus
* Fix Illustration Resource
* npm run format
* Update showFRE related logics in both backend and frontend
* FE Review Changes
* Update API method name to SetTabFocusEnabled
---------
Co-authored-by: Jocelyn Liu <yrliou@gmail.com>
This class was mirroring data in the continuation file. This change
eliminates this duplication of sources, and moves all the post-apply
checks into the data type itself.
This change also renames the data stucture and field to something more
appropriate to the use of the data itself.
Resolves https://github.com/brave/brave-browser/issues/45303
This change removes `MediaImageLoader` which is an old piece of Firefox code that has been since removed which would pre-load any images found in `og:image` into the web image cache despite it never being used
There was a previous refactoring in this code, and for some reason this
only use of `repository.chromium()` was left behind, which has caused a
crash in the pipeline.
Resolves https://github.com/brave/brave-browser/issues/45293
The addition of this argument will allow us to checkout a different
Chromium version, as a tantive version. This is useful when generating
the toolchain for a version bump that the branch itself is not fully
up-to-date with, but it is close enough to provide hermetic toolchains
necessary to run the toolchain job with.
Resolves https://github.com/brave/brave-browser/issues/45237
This PR adds tests for `Version` to `brockit`. For convenience,
`Version` has been moved into its own module, and also a few other bits
and pieces that were associated with it.
This change also touches a lot on `Repository`, because these two
modules make heavy use of a common test machinery for the two. This
means adjusting both tests to make better reuse of code.
Finally, `Repository.chromium()`/`Repository.brave()` are being changed
into globals inside `repository`. This is to avoid instatiations on each
use, and to follow the advise in
https://google.github.io/styleguide/pyguide.html#2174-decision regarding
the use of `@classmethod`
Resolves https://github.com/brave/brave-browser/issues/45231
Adding this hook into the repo that could be used by anyone to have a
standardised way to add tags into commit messages. This also provides a
way to add chromium culprits into changes.
Resolves https://github.com/brave/brave-browser/issues/45015
This change corrects an issue with our current rebase operation, and its
reliance on `git merge-base fork-point`, which gets off-base when the
upstream branch for a given branch (say `cr137`, `cr138`) gets rebased
against their own upstream branch and force pushed. At that point, the
fork point returned by git is wildly off and behind where it should
actually be.
This change adds `--to-ref`/`--from-ref` as a better way to select the
range of changes that we want to rebase. With `--to-ref` it defaults to
`@upstream` when nothing is provided, and it represents the branch we
are rebasing the version on top.
With `--from-ref` we default to `@previous-major` when dealing with
major lifts, or just to `@previous` when dealing with minor bumps.
`@previous-major` is being introduced to find exactly the first change
that changed the major version.
This PR also removes the "dry-run" attempt in determining if there could
be conflicts when rebasing a branch as that warning was entirely
off base.
Resolves https://github.com/brave/brave-browser/issues/45226
Initially the menu was too narrow to fully fit items localized in
German, so we increased the width to the regular menu width of 800.
However users indicated that it was now too wide. This change reduces
the width to 500, which is still enough to fit the German l10n.
cdesouza-chromium