chore: untrack the quality reports this package generates - #5
Merged
Merged
Conversation
`.complexity/` and `.documentation/` hold output from provide-testkit's own quality tooling -- `quality/complexity/analyzer.py` writes `complexity.json` into its artifact directory -- so any checkout that runs the suite regenerates them and they show as modified from then on. They had been sitting dirty in the working tree for that reason. Nothing reads them: the only matches for those names in the repository are the `provide.testkit.quality.complexity` module namespace, not the directories. And they entered in a single commit, eb3a6f1, a release sweep that picked them up along with everything else rather than a decision to track them. The files stay on disk; they are simply no longer the repository's business.
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.
.complexity/and.documentation/hold output from provide-testkit's own quality tooling —quality/complexity/analyzer.pywritescomplexity.jsoninto its artifact directory — so any checkout that runs the suite regenerates them and they read as modified from then on. They had been sitting dirty in the working tree for exactly that reason.Nothing reads them. The only matches for those names anywhere in the repository are the
provide.testkit.quality.complexitymodule namespace, not the directories.Nothing chose to track them. They entered in a single commit —
eb3a6f1 feat(release): restore content suite and finalize v0.4.0 release environment— a release sweep that picked them up along with everything else. One commit has ever touched them.The files stay on disk; they are simply no longer the repository's business.
🤖 Generated with Claude Code