Douglas Schveninger

I agree with the steps. We will review the steps and submit a PR. Thank you.

I will have to looking into that and what it exhaust over email address. Will review and get back. Thanks.

I was thinking of allowing a type that contained a map[string]sting being passed into RunSpecs to attaching it to the Suite for the Reporter to support attaching this metadata to...

We have been reviewing the code and we are thinking if the https://github.com/onsi/ginkgo/blob/d696c7b753a2107ccbe5ddbabaab256539a2d1fb/types/types.go#L15 Report would have a map[string]string called SuiteProperties we could add key vale pairs in the ReportBeforeSuite function....

Looking over the focus process it looks like the https://github.com/onsi/ginkgo/blob/master/internal/focus.go#L59 function is what sets the Spec skip Boolean. I was wondering if we could attach reason to the Spec or...

We are using ginkgo for our end 2 end testing of a large environment that contains many sub products and the suites are maintained by over 100 engineers. We have...

Here is an outline of what I think I would do: Add SkipReason to Spec in spec.go in internal Update focus.go to to define why the CLI will be skipping...

No apologies necessary, we appreciate the product you have in the amount of support that you give it. We do use the skip in IT at run time, after spec...

The other issue we are having is we are still using V6. Is there a why to place the Megalinter version in the schema so we do not have the...

Let's us try some of your suggestion. Thank you for the ideas. Once we find the best direction, we will update this issue and close it if you do not...