Repository navigation
intake: accept new Markdown files next to a tracked file without a component manifest (#364) - #373
Merged
Conversation
…mponent manifest (#364)
Owner
Author
|
Adversarial review: no HIGH or MEDIUM findings. The Markdown rule runs after the existing traversal, directory and symlink checks, and needs a tracked regular file (not a symlink or submodule) in the same directory. Dot-directories keep the manifest rule. MarkdownNewFiles joins the plan digest and is omitted when empty, so older digests are unchanged. LOW, not fixed: Integration: origin/main is still the base, 1031809. |
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.
Implements issue #364.
Molecule:
mol-364-305f3dbfe2a4cef47ab40597Formula:
forgecell-github-issueBase:
10318096141ed061379a8f93f6657d991083b7beDelivery:
9265c1b0355f8f0c585c2faf6ee7878e9e197e00Awaiting exact-commit CI and human review. Harness-reported checks are not independent CI evidence. No merge, deployment or issue closure is authorized.