-
-
Notifications
You must be signed in to change notification settings - Fork 929
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #6842 from stylelint/fix-function-no-unknown-false…
…-positives-for-unspaced-operators-against-nested-brackets--resourceful-kangaroo-ec239dde9a Fix `function-no-unknown` false positives for unspaced operators against nested brackets
- Loading branch information
Showing
3 changed files
with
37 additions
and
22 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,5 @@ | ||
--- | ||
"stylelint": patch | ||
--- | ||
|
||
Fixed: `function-no-unknown` false positives for unspaced operators against nested brackets |
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
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
6f421a0
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.
@romainmenke Sorry for my late notice. Could you please usually "squash and merge" pull requests as the maintainer guide says?
However, I appreciate your effort and contribution to this project! 😊
6f421a0
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.
Thank you @ybiquitous for pointing this out, I will use the correct merge method from now on :)
Is this something that can be enforced in settings, so that only squash and merge is available?
6f421a0
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.
It would be ideal, but we occasionally want to use "merge", for example, when merging a long-living branch to implement a big feature and preserve each commit. 😅
I wish we had a better way... 🤔