Add --no-config option
#250
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jasonmccreary
force-pushed
the
no-config
branch
from
e1d309d to
6b87366
Compare
itinerare
pushed a commit
to itinerare/Alcyone
that referenced
this pull request
Feb 26, 2024
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [laravel/pint](https://laravel.com) ([source](https://github.com/laravel/pint)) | `1.13.11` -> `1.14.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>laravel/pint (laravel/pint)</summary> ### [`v1.14.0`](https://github.com/laravel/pint/blob/HEAD/CHANGELOG.md#v1140---2024-02-20) [Compare Source](laravel/pint@v1.13.11...v1.14.0) - Add `--no-config` option by [@​jasonmccreary](https://github.com/jasonmccreary) in laravel/pint#250 </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy4yMTQuMCIsInVwZGF0ZWRJblZlciI6IjM3LjIxNC4wIiwidGFyZ2V0QnJhbmNoIjoiZGV2ZWxvcCJ9--> Reviewed-on: https://code.itinerare.net/itinerare/Alcyone/pulls/6 Co-authored-by: Amadeus[bot] <amadeus@itinerare.net> Co-committed-by: Amadeus[bot] <amadeus@itinerare.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently,
pintwill merge any project config with the--presetoption. This was slightly unexpected and makes it difficult to quickly use one of the presents from within a project that has a custompint.jsonconfig.You can get around this by passing an invalid path to
--config. But that's a bit hacky. I felt a--no-configoption was nice and provides an explicit way to preventpintfrom merging any project config.For example, to apply the
laravelpreset to a set of stub files:This is indeed a real world use case where a project has it's own rules configured within
pint.json, but contains stub files which are formatted to thelaravelpreset.