Provide a detailed description of the proposed feature

On https://docs.brew.sh/Formula-Cookbook there is a terminology list. I suggest copying it on https://docs.brew.sh/Manpage or at least adding a link

What is the motivation for the feature?

I started by reading man. I could not find anything defining casks in it. I know I can install a formula and don't know what a formula is, what c

We have currently simple GitHub page, but we need to think about it's update with some better design.

Currently register looks like:

   private static <T> void register(Map<T, T> substitutions, T annotated, T original, T target) {
        if (annotated != null) {
            guarantee(!substitutions.containsKey(annotated) || substitutions.get(annotated) == original || substitutions.get(annotated) == target, "Already registered: %s", annotated);
            substitutions.put(annotated,

Is your feature request related to a problem? Please describe.

I'm kicking the tires on changing our Gemfile to gems.rb. However, we have many internal gems within our monorepo and it just occurred to me that it would be cool to have a configurable cop that enforces one or the other.

Describe the solution you'd like

A cop that checks to make sure you have a Gemfile or a `gems.

I am trying to write my own custom route matcher and using the example in the readme, I receive the following error:
AllButPattern can't be coerced into Mustermann::Pattern (TypeError)

Here is my example code:

require 'sinatra'

get '/index' do
  'Hello world!'
end

class AllButPattern
  Match = Struct.new(:captu

Getting an error here when using the remove_promotion_line_items method. Seems like it should be using variant rather than item
https://github.com/spree/spree/blob/8ca9ec736a471b66f66d718b157be69946f8c5fc/core/app/models/spree/promotion_handler/coupon.rb#L78

Steps to reproduce

Run asdf. In help output a line is printed for the asdf env command:

asdf env <command> [executable]      Prints or runs an executable under a command environment

I would assume <command> is an arbitrary command. But from what I can tell needs to be a plugin name or a shim name? I'm also not sure how this differs from executing the shim directly.

FY