chore: clean public repo boundary - #31
Merged
Merged
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
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.
Summary
.solo-misefragments, and the stale solo-mise banner from the public treesrc/brigade/templates/and tests undertests/README.mdMANIFEST.into includesrc/brigade/templatesinstead of the oldsrc/solo_mise/templatespathVerification
.venv/bin/python -m pytest -q-> 262 passedPYTHONPATH=$HOME/repos/content-guard/src python3 -m content_guard scan . --policy $HOME/repos/content-guard/policies/public-repo.json-> Clean, 67 files checkedgit diff --cached --check-> passed.venv/bin/brigade doctor --target .-> passed.venv/bin/python -m build --sdist --wheel-> built sdist and wheel; existing setuptools license deprecation warnings onlyNote
This cleans the current public tree. It does not purge prior Git history. If any previously pushed content is truly sensitive, handle that separately with history rewrite or repository visibility controls.