What happened to --ci?

[nhaynes]

What happened to the --ci option to prevent ->only() from impacting continuous integration environments?

It seems to have disappeared from the docs around the time V2 came out but there is no mention of it in the Upgrade Guide.

It's disappearance caused some issues for one of my projects. Is there a new preferred way to prevent only() from impacting CI envs (aside from not checking them in)?

[nhaynes]

I see the --ci option is included in the Environment plugin file but this Plugin does not appear to be getting loaded when I run Pest:

// Pest.php

dd(\Pest\Plugin::$callables);

---

I've tried registering the plugin myself but the --ci argument is still ignored:

// Pest.php

\Pest\Plugin::uses(\Pest\Plugins\Environment::class);

// ExampleTest.php

test('example', function () {
    expect(true)->toBeTrue();
});

test('example with only', function () {
    expect(true)->toBeTrue();
})->only();

---

Which Plugins are supposed to be loaded by default and how do you get the Environment plugin to work properly?

[nhaynes]

The loading of the Plugin does not appear to be the problem as the Environment::name() value is returned correctly as CI when specifying the --ci flag so this Plugin is working.

It appears that the logic of the feature was simply removed during the refactor of the ->only() method: a61db76

I'm not sure if this was intentional or not so I submitted a PR (#1082) to address it.