New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Composer.json without require entries should not be an error #78
Comments
Hey @JoshuaBehrens. Thanks for reaching out. Of course this doesn't make sense at all. I will see to it and change the behavior to a valid exit code. 👍 |
Looking forward to it. When you need any help from my side just give me a note. I'd really like to use this tool 👍 |
Merged into |
Works like expected. Thanks for the fast responses and fixes. Keep up the great commitment 🥇 this is a very helpful tool that more people should be aware of 💯 |
Thank you ❤️ |
🥳 |
Describe the bug
A composer.json with no require entries seems to be a problem as the exit code is non zero and thus kills CI or other following scripts. Having nothing to check should not be per-se an error. When nothing is there to be checked anymore it is an error having this tool still required, check. When nothing is there to be checked yet is it not an error. This keeps me from preparing a repository so I can't use this tool without having a problem that I am not aware of yet.
Error dump
composer.json
Command
Log
The text was updated successfully, but these errors were encountered: