Skip to content

build: don't format api golden files #15568

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
Mar 22, 2019

Conversation

crisbeto
Copy link
Member

@crisbeto crisbeto commented Mar 21, 2019

As discussed a while ago, we shouldn't be formatting the API golden files, because the task that checks them verifies that the files are exactly the same and the formatting throws it off.

As discussed a while ago, we should be formatting the API golden files, because the task that checks them verifies that the files are exactly the same and the formatting throws it off.
@crisbeto crisbeto added pr: merge safe target: patch This PR is targeted for the next patch release labels Mar 21, 2019
@crisbeto crisbeto requested a review from jelbourn as a code owner March 21, 2019 20:33
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Mar 21, 2019
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 added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Mar 21, 2019
@andrewseguin andrewseguin merged commit 7ee03fe into angular:master Mar 22, 2019
andrewseguin pushed a commit that referenced this pull request Mar 25, 2019
As discussed a while ago, we should be formatting the API golden files, because the task that checks them verifies that the files are exactly the same and the formatting throws it off.
@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 10, 2019
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 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