pest --ci option doesn't exist and no-ops?
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 56
- Forks
- 180
- PR merge metrics
- No merged PRs in 30d
Description
I was going to set up CI/CD with Pest to help enforce keeping expectations up to date. However, the guide is rather confusing, as I can't find out what ./vendor/bin/pest --ci would do differently to just ./vendor/bin/pest, due to there seemingly being no mention of what this --ci option does anywhere.
Maybe I'm just blind, but I really can't find it, and running the command with --ci doesn't make any visible difference in output.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the continuous-integration guide linked in the issue and compare the documented ./vendor/bin/pest --ci command with ./vendor/bin/pest. Verify what, if anything, the --ci option changes, then update the guide so its behavior and purpose are clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100