-
Notifications
You must be signed in to change notification settings - Fork 894
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
fix: remove unnecessary console.log statement #8437
Conversation
🦋 Changeset detectedLatest commit: 283da47 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Hey @TheeKia, thanks for submitting this PR. Could you add a changeset? It's required for this change to cause a version bump and included in the next release. You can do this by running |
Hi @dlarocque, I’ve added the changeset as requested, which includes a patch bump for @firebase/app. This is my first PR for Firebase, so please let me know if there’s anything else needed or any further adjustments I should make. Thank you for your guidance! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Following the discussion in issue #8436, I’ve removed an unnecessary console.log statement that appears to have been inadvertently included in a recent commit