[5.3.1] add change to allow blaze info to skip Starlark build settings that start with --no prefix

[ghost]

Resolves #16257 .

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[ghost]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Bah. I signed the CLA and have had PRs merged before. However, this was a backport/cherry-pick of a commit that originated from Google. I left the original authorship as-is because I didn't author the code. What is the best way to proceed?

[sgowroji]

Hello @beasleyr-vmw, Could you please rescan and verify the CLA on this PR and share for final review. Thanks!

[fmeum]

@sgowroji The problem here is that the commit is cherry-picked from a Googler's commit and thus uses their author email, which is what the CLA bot checks against. But of course the googler hasn't signed the CLA. What is the best course of action in this case?

[Wyverald]

The CLA check has been overridden by "a googler" (don't know who did that). So this should be good to go.