okf: add optional .okfignore convention (SPEC 3.2)#190
Open
manumishra12 wants to merge 1 commit into
Open
Conversation
Adds an optional ignore-file convention so producers can mark files or directories that consumers and enrichment agents SHOULD skip when walking a bundle (drafts, scratch notes, large binaries). Uses gitignore-style patterns and never affects conformance: matching files are skipped, not forbidden. Additive and backward-compatible (per SPEC 11). Addresses GoogleCloudPlatform#77.
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.
What
Adds an optional
.okfignoreconvention as a new subsection (SPEC section 3.2) so producers can mark files or directories that consumers and enrichment agents SHOULD skip when walking a bundle — drafts, scratch notes, large binaries, and similar non-knowledge files.Semantics
#comments ignored.Spec-only, additive, and backward-compatible (SPEC section 11 minor-version rules). Reference-tooling support can follow.
Addresses #77.