docs(takeFirstBy): fix error in comment#1290
Merged
Merged
Conversation
|
|
✅ Deploy Preview for trusting-lumiere-9c7fad ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1290 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 174 174
Lines 1622 1622
Branches 392 383 -9
=========================================
Hits 1622 1622 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
commit: |
|
🎉 This PR is included in version 2.33.7 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make sure that you:
src/index.tsdocs/src/content/mappingfor both Lodash and Ramda.We use semantic PR titles to automate the release process!
https://conventionalcommits.org
PRs should be titled following using the format:
< TYPE >(< scope >)?: descriptionAvailable Types:
feat: new functions, and changes to a function's type that would impact users.fix: changes to the runtime behavior of an existing function, or refinements to it's type that shouldn't impact most users.test: tests-only changes (transparent to users of the function).docs: changes to the documentation of a function or the documentation site.build,ci,chore, andrevert: are only relevant for the internals of the library.For scope put the name of the function you are working on (either new or
existing).