Is it considered general practice to include generated contents of /public in source control?
Just gut-checking, my thoughts were public and its contents below should always be handled at time of deployment and excluded from source control, but updates to filament are re-generating the public/css and public/js folders. I have a vanilla deployment configuration in Laravel Forge, should be I committing these folders?
1 Reply
I wouldn't add them and make them part of deployment