Richard Hallows

> Could you check the changes when you have some free time? @sw1tch3roo I hope to have time to review the changes in a couple of weeks, as I'm currently...

Thanks for the request. Let's add a new rule for saturation. - Name: `saturation-notation` - Primary option: `"percentage"|"number"` - Secondary options: None - Autofixable: Yes - Message: `Expected "${unfixed}" to...

> For example I'd like to enforce the use of numbers everywhere, including `rgb`, `oklab`, and `hwb` Am I right in thinking you need this for the MDN Web Docs?...

Welcome back @mattxwang! I'm sorry to hear about the upheaval, and I hope things are better now. It'd be great if you took a stab at this issue. Fantastic sleuthing,...

Thank you for chiming in @Mouvedia. > If it has been tested to be compatible with these LLMs Let's decide if housing an official server within our organisation and documenting...

I share your sentiments about LLMs, @romainmenke. It feels like the genie is out of the bottle, though, and, like you said, we can try to minimise bad outcomes by...

If you add me to the GitHub repo and the npm package, I should be able to transfer them. I'll wait a bit longer before actually doing the transfer, though,...

@unikitty37 Thank you for the report and clear write-up. You can use something like: ```js module.exports = { "rules": { "declaration-property-value-disallowed-list": [{ "font-weight": ['normal', 'bold'], "font-style": ['italic', 'oblique'], }, {...

> I'm ready to fix the other part of https://github.com/stylelint/stylelint/issues/8780 once this PR gets merged Fantastic, thank you! We can now add the same option to `custom-property-empty-line-before` in a follow-up...

@danieldelcore Thanks for the report and clear write-up. > I found that exporting my rules like so fixed the issue for me, but would still be nice if this could...