feat: Add .gitignore rules to prevent nested .editorconfig files #195
Conversation
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
Member
Template Repository Sync Report
guard
|
Co-authored-by: samtrion <3283596+samtrion@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] feature: Extend
feat: Add .gitignore rules to prevent nested .editorconfig files
Aug 18, 2025
.gitignore to prevent nested .editorconfig files
samtrion
added
state:ready for merge
Member
|
@copilot All commit messages must follow the guidelines for conventional commits https://www.conventionalcommits.org/en/v1.0.0/ |
Contributor
Author
The commit message "feat: Add .gitignore rules to prevent nested .editorconfig files" follows the conventional commits specification with the format |
Member
Yes, but the first commit "Initial plan" is not following the convention |
Contributor
Author
You're correct - the "Initial plan" commit doesn't follow conventional commit format. Unfortunately, I cannot rewrite git history (no force push capability) to fix this commit message. The commit should have been something like |
samtrion
approved these changes
Aug 18, 2025
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 change extends the
.gitignorefile to prevent nested.editorconfigfiles from being created and committed in subdirectories, while preserving the existing root.editorconfigfile.Problem
When using this template across multiple DailyDevOps repositories, developers might accidentally create additional
.editorconfigfiles in subdirectories. This can lead to:.editorconfigsettings are being appliedSolution
Added two targeted
.gitignorerules:**/.editorconfig- Ignores all.editorconfigfiles in any subdirectory!/.editorconfig- Explicitly allows the root.editorconfigfile to remain trackedTesting
Verified the solution works correctly by:
.editorconfigfiles in various nested directory structures (src/,src/MyProject/,src/MyProject/Sub/).editorconfigfiles are ignored by git.editorconfigfile remains tracked and unaffectedgit check-ignoreto validate the patterns work as expectedThe root
.editorconfigfile containsroot = truewhich makes it the authoritative configuration file for the entire repository, making nested files unnecessary and potentially problematic.Fixes #194.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.