Repository navigation
Do not auto-create ecs.php when --config is provided - #163
Merged
Merged
Conversation
TomasVotruba
force-pushed
the
tv-skip-config-create-on-config-flag
branch
from
October 8, 2026 10:39
22bdae6 to
6f67e4d
Compare
TomasVotruba
enabled auto-merge (squash)
October 8, 2026 10:39
This file contains hidden or 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
1 participant
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.
When
--config <path>points to a config outside the current directory and that config registers no checkers (or is not found), ECS fell back to the auto-init path and offered to generate a newecs.phpin the cwd, instead of honoring the explicitly provided config.Guard the auto-create step so it only runs when no
--configflag was given. With an explicit--config, ECS now always uses that config and never generates a new one.