Harden generated artefact boundaries and stop tracking exported inventory packages - #12
Merged
Merged
Conversation
Copilot created this pull request from a session on behalf of
goldjg
June 30, 2026 22:55
View session
goldjg
marked this pull request as ready for review
June 30, 2026 22:56
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.
This change closes gaps in the repository’s generated-artifact boundary so local databases, cloned spec corpora, SARIF/results, inventory exports, and packaged shard outputs are not accidentally committed. It also aligns the repo’s cARL/docs guidance with the actual ownership model for those artifacts.
Ignore generated inventory outputs more completely
inventory/ignores beyond JSON exports to also cover shard directories and packaged ZIP outputs.inventory/.gitkeepas the only tracked placeholder in that directory.Document artifact ownership in
.gitignoreresults/→ query execution / security scan workflowazure-rest-api-specs/→ refresh/export inputsdatabase/→ refresh/build pipelineinventory/→ export workflowsRemove tracked generated exports
inventory/so the ignore rules are effective in practice, not just in theory.Reconcile contributor and cARL guidance