You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I already have Enlighten fully set up and the documentation's getting generated well.
As a team, we always have to run the enlighten on the local and do export and commit all of the changes to the git. so the clients can see the docs on the web.
Recently I have tried to run the tests on our GitLab CI and upload the enlighten database to our server after a complete full test run, but the problem is that our CI job does not recognize the failed stopped test when using command php artisan enlighten, and shows the CI job as passed. while it should show not passed.
I wonder if we can use ./vendor/bin/phpunit as it let the CI job get flagged as not passed when a test fails. Or find a way to do the same on the enlighten command.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I already have Enlighten fully set up and the documentation's getting generated well.
As a team, we always have to run the enlighten on the local and do export and commit all of the changes to the git. so the clients can see the docs on the web.
Recently I have tried to run the tests on our GitLab CI and upload the enlighten database to our server after a complete full test run, but the problem is that our CI job does not recognize the failed stopped test when using command
php artisan enlighten
, and shows the CI job as passed. while it should show not passed.I wonder if we can use
./vendor/bin/phpunit
as it let the CI job get flagged as not passed when a test fails. Or find a way to do the same on the enlighten command.The text was updated successfully, but these errors were encountered: