fix: do not default on content-range #456
Merged
Conversation
This file contains 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
fenos
force-pushed
the
fix/remove-default-content-range
branch
from
17f2ae5 to
ac0fc48
Compare
Pull Request Test Coverage Report for Build 8721710899Details
💛 - Coveralls |
fenos
force-pushed
the
fix/remove-default-content-range
branch
from
ac0fc48 to
0d5eeaa
Compare
pcnc
approved these changes
Apr 17, 2024
fenos
force-pushed
the
fix/remove-default-content-range
branch
from
0d5eeaa to
79373f8
Compare
|
🎉 This PR is included in version 1.0.8 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What kind of change does this PR introduce?
Bug fix
What is the new behavior?
Remove default on content-range