Skip to content

build: fix lint error #28907

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
Apr 18, 2024
Merged

build: fix lint error #28907

merged 1 commit into from
Apr 18, 2024

Conversation

zarend
Copy link
Contributor

@zarend zarend commented Apr 18, 2024

No description provided.

@zarend zarend requested a review from andrewseguin as a code owner April 18, 2024 18:33
@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label Apr 18, 2024
@zarend zarend added the target: patch This PR is targeted for the next patch release label Apr 18, 2024
@zarend zarend removed the request for review from andrewseguin April 18, 2024 20:03
@zarend zarend added the action: merge The PR is ready for merge by the caretaker label Apr 18, 2024
@zarend zarend merged commit b5c68e9 into angular:main Apr 18, 2024
zarend added a commit that referenced this pull request Apr 18, 2024
(cherry picked from commit b5c68e9)
@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 May 19, 2024
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 area: build & ci Related the build and CI infrastructure of the project target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants