Skip to content

build: clean up uses of integers as booleans in Bazel files #20388

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

Merged
merged 1 commit into from
Aug 25, 2020

Conversation

crisbeto
Copy link
Member

Fixes a few places that are inconsistent by using 1 instead of True.

Also fixes one place where we were using the incorrect wording in a license header.

Fixes a few places that are inconsistent by using `1` instead of `True`.

Also fixes one place where we were using the incorrect wording in a license header.
@crisbeto crisbeto added merge safe P4 A relatively minor issue that is not relevant to core functions target: patch This PR is targeted for the next patch release labels Aug 21, 2020
@crisbeto crisbeto requested review from jelbourn and a team as code owners August 21, 2020 21:56
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 21, 2020
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Aug 21, 2020
Copy link
Member

@devversion devversion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Looks like there is no buildifier rule we can enable: https://github.com/bazelbuild/buildtools/blob/master/WARNINGS.md

Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jelbourn jelbourn merged commit 6103b74 into angular:master Aug 25, 2020
jelbourn pushed a commit that referenced this pull request Aug 25, 2020
Fixes a few places that are inconsistent by using `1` instead of `True`.

Also fixes one place where we were using the incorrect wording in a license header.

(cherry picked from commit 6103b74)
annieyw pushed a commit to annieyw/components that referenced this pull request Aug 31, 2020
…20388)

Fixes a few places that are inconsistent by using `1` instead of `True`.

Also fixes one place where we were using the incorrect wording in a license header.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P4 A relatively minor issue that is not relevant to core functions target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants