Skip to content

[9.x] Vendor publish flag that restricts to only existing files#43212

Merged
taylorotwell merged 2 commits intolaravel:9.xfrom
intrepidws:vendor-publish-only-existing-files
Jul 19, 2022
Merged

[9.x] Vendor publish flag that restricts to only existing files#43212
taylorotwell merged 2 commits intolaravel:9.xfrom
intrepidws:vendor-publish-only-existing-files

Conversation

@intrepidws
Copy link
Contributor

I often find myself overriding a specific view file for a vendor package and then losing track of whether the package eventually updated that file or not. While I could simply run php artisan vendor:publish --tag=filament-config --force, that publishes ALL of the view files when I am only interested in files that I have created manually. Since many packages have dozens, if not hundreds, of view files - this can be burdensome.

This PR introduces a new --existing flag that instructs the vendor:publish command to only publish and overwrite files that already exist.

I did consider naming the flag --force-only-existing, or some variation thereof and would be open to any change you felt would be more appropriate.

@taylorotwell taylorotwell merged commit 5a99c2d into laravel:9.x Jul 19, 2022
@intrepidws intrepidws deleted the vendor-publish-only-existing-files branch July 19, 2022 17:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants