Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: do not pass --{enable,disable}-features twice when user-provided #11230

Merged
merged 3 commits into from Oct 23, 2023

Conversation

thiagowfx
Copy link
Contributor

Currently, whenever the user provides:

args: '--disable-features=TestDisableFeatures'

The --disable-features flag appears twice in chrome arguments.

Make it appear only once, by merging them.

Ditto for --enable-features.

Fixed: #11208

Currently, whenever the user provides:

    args: '--disable-features=TestDisableFeatures'

The --disable-features flag appears twice in chrome arguments.

Make it appear only once, by merging them.

Ditto for --enable-features.

Bug: #11208
@thiagowfx thiagowfx enabled auto-merge (squash) October 23, 2023 13:05
@thiagowfx thiagowfx merged commit edec7d5 into main Oct 23, 2023
50 checks passed
@thiagowfx thiagowfx deleted the thiagowfx/features branch October 23, 2023 13:27
@release-please release-please bot mentioned this pull request Oct 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Bug] Merging disabled and enabled features does not remove additional enable/disable args
3 participants