Ignore docker-compose.override.yml in .gitignore for flexible local setups #54516
+1
−0
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
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.
This PR updates .gitignore to exclude docker-compose.override.yml, allowing contributors to use custom Docker configurations without affecting the repository.
Why this change?
Laravel’s core repository includes a docker-compose.yml, but contributors might need additional configurations (e.g., adding a PHP service for running tests in Docker).
docker-compose.override.yml is a built-in mechanism in Docker Compose that lets users extend the default setup without modifying the main file.
By ignoring this file, contributors can define their own overrides without accidentally committing personal configurations.
This makes local development more flexible while keeping the repository clean. 🚀