Skip to content

build: fix wrong import path #22510

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Apr 19, 2021
Merged

build: fix wrong import path #22510

merged 1 commit into from
Apr 19, 2021

Conversation

@crisbeto
Copy link
Member

@crisbeto crisbeto commented Apr 19, 2021

Fixes a path that is wrong, because the PR was opened before we renamed the file.

@crisbeto
build: fix wrong import path
363b709 
Fixes a path that is wrong, because the PR was opened before we renamed the file.
@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround merge safe target: minor This PR is targeted for the next minor release labels Apr 19, 2021
@crisbeto crisbeto requested a review from wagnermaciel April 19, 2021 19:40
@crisbeto crisbeto requested a review from andrewseguin as a code owner April 19, 2021 19:40
@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Apr 19, 2021
wagnermaciel
wagnermaciel approved these changes Apr 19, 2021
View reviewed changes
Copy link
Contributor

@wagnermaciel wagnermaciel 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 Apr 19, 2021
@wagnermaciel wagnermaciel merged commit 94ea13c into angular:master Apr 19, 2021
zelliott pushed a commit to zelliott/components that referenced this pull request Apr 19, 2021
@crisbeto @zelliott
build: fix wrong import path (angular#22510)
e668309 
Fixes a path that is wrong, because the PR was opened before we renamed the file.
@angular-automatic-lock-bot
Copy link

angular-automatic-lock-bot bot commented May 20, 2021

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 May 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Reviewers

@wagnermaciel wagnermaciel wagnermaciel approved these changes

@andrewseguin andrewseguin Awaiting requested review from andrewseguin

Assignees

No one assigned

Labels

action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement P2 The issue is important to a large percentage of users, with a workaround target: minor This PR is targeted for the next minor release

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@crisbeto @wagnermaciel