Skip to content
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

chore: cleanup bazel #4675

Merged
merged 1 commit into from
Jan 17, 2025
Merged

chore: cleanup bazel #4675

merged 1 commit into from
Jan 17, 2025

Conversation

timdeschryver
Copy link
Member

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[x] Other... Please describe: cleanup 🧹

What is the current behavior?

Closes #

What is the new behavior?

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

Other information

As mentioned in #4670 I thought I had seen a few more references to yarn.
It turns out it was just a lock file that was used within our bazel setup.
This PR removes some leftovers because we're not using it anymore 🧹.

Copy link

netlify bot commented Jan 16, 2025

Deploy Preview for ngrx-io canceled.

Name Link
🔨 Latest commit 813f164
🔍 Latest deploy log https://app.netlify.com/sites/ngrx-io/deploys/67895ae7a116d400082ce2a8

Copy link
Member

@markostanimirovic markostanimirovic left a comment

Choose a reason for hiding this comment

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

🧹

@brandonroberts brandonroberts merged commit a5d2096 into main Jan 17, 2025
10 checks passed
@brandonroberts brandonroberts deleted the chore/cleanup-bazel branch January 17, 2025 02:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants