Queue dsh-permission-rules@0.4.2 from #9 (pending review) - #10
Open
PerryLink wants to merge 1 commit into
Open
Conversation
This was referenced Aug 15, 2026
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.
Automated intake for submission Issue #9 (
[Submission] dsh-permission-rules@0.4.2).github-actions[bot]committed the pending-review record, the typed harness plan, and the queue update to theautomation/intake-9-31873331572branch (commit7138f47).GitHub Actions is not permitted to create or approve pull requests), and same-repo branches cannot be PR'd by non-collaborators, so this PR carries the exact bot-prepared commit from a fork branch — no content changes beyond what the automation committed.Submission facts (from the issue): pinned commit
b0132581bb59ebdd833798f2b457b66a171fff70,profile-bundle/harness-profile, transactional install with generation rollback, RC.6 compatibility,/rulescommand capability. Runtime lifecycle evidence is not yet produced (author environment is Windows; the current isolated executor requires macOSsandbox-exec), so evidence paths remainnulland verification stays untested until a Harness-produced run exists.