Wolfgang Teuber

temp. work-around: ``` git reset --hard git reset --soft git add -A git tree git reset --hard ```

I would have liked a warning or error message like this... I now used https://github.com/adrienverge/yamllint for checking for duplicate keys.

@tenderlove you mentioned backwards compatibility... Instead raising an error, just (optionally) printing out a warning wouldn't brake backwards compatibility but help many people manage their yaml files. What do you...

I helped programmatically avoiding this issue by writing and introducing a normalized YAML format in the projects I am involved in. Maybe you find this helpful, too: https://github.com/Sage/yaml_normalizer @imaginejosephishak

+1 searching gist **filenames**, **descriptions** in GistPad would already be a great improvement (contents would be nice, but I can see how it complicates things)

Hi @fatkodima, thanks for your consideration. We haven't checked all of them, but have come across another performance cop that seems to lower performance in ruby 3.1.2p20 (both arm64-darwin21 and...

We benchmarked all currently available RuboCop Performance cops and found three cops that actually **worsen performance** in ruby 3.2.0. env | cops -- | -- ruby_3.2.0, x86_64_Linux | Performance/**ArraySemiInfiniteRangeSlice** ruby_3.2.0,...

Thanks a lot for you PR, @marcpursals! I'll have a detailed look at this PR later this week. Here are 2 early requests. 1. Gem files should not be part...

Sounds great. For smaller projects, we don't have strict contribution guidelines. I'll double-check Sage's open source policies to allow gem owners outside the organisation.

I had a chance to look at the changes. Most of it looks really great and is fast too, great work! Also, text fields for arrays work just like expected....