[Rulesets](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets#branch-and-tag-rulesets) would also work. You create one targeting all tags and simply restrict tag cr...Earlopain (Earlopain _)
It gets confused for syntax introduced in https://bugs.ruby-lang.org/issues/20925 But it actually should be a plain method call. `!`/`?` are not valid as part of an identifier, methods however allow them as the last character. Fixes [Bu...Earlopain (Earlopain _)
They currently complain that the parent method is not forwarding. But the actual problem is that these types of arguments simply don't accept `...` Fixes [Bug #21927] https://github.com/ruby/prism/commit/0aa2363331Earlopain (Earlopain _)
Applied in changeset commit:git|54eb330f8cc9f5a5b67ccfa5247cd8b98fb1ef44. ---------- [ruby/prism] Correctly handle `and?` and similar on ruby 4.0 It gets confused for syntax introduced in https://bugs.ruby-lang.org/issues/20925 But it ...Earlopain (Earlopain _)
It gets confused for syntax introduced in https://bugs.ruby-lang.org/issues/20925 But it actually should be a plain method call. `!`/`?` are not valid as part of an identifier, methods however allow them as the last character. Fixes [Bu...Earlopain (Earlopain _)
```rb Ripper.lex("foo\nand?") => [[[1, 0], :on_ident, "foo", CMDARG], [[1, 3], :on_ignored_nl, "\n", CMDARG], [[2, 0], :on_ident, "and?", ARG]] ``` Presumably this is because until the `?` is encountered, it is considered syntax as...Earlopain (Earlopain _)
writes" (https://github.com/ruby/prism/pull/3960) This reverts commit https://github.com/ruby/prism/commit/4e71dbfc7bd9. And also add a regression test. Seems like currently prism parses these the same that parse.y does. https://githu...Earlopain (Earlopain _)