feat(workspace): add explicit setup commands - #467
Merged
Conversation
Deploying allagents with
|
| Latest commit: |
1e6dbfc
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://0c8e3c54.allagents.pages.dev |
| Branch Preview URL: | https://feat-herdr-workspace-tooling.allagents.pages.dev |
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
setuplist toworkspace.yaml, with string shorthand and object entries usingrun,platforms, andarchitecturesallagents workspace setupexecution with platform/architecture selection, command display, sequential execution, deterministic JSON output, and first-failure handlinginit,update, andsyncbecause remote workspace templates are untrustedherdrdev/herdrskillConfiguration
Architecture selectors use Node
process.archnames. Herdr's platform installers already detect x64 versus ARM, so the example does not need architecture-specific commands.Verification
bun test— 1488 passed, 5 skipped, 0 failedbun run typecheckbun run lintbun run buildWorkspaceConfigSchema; Linux/macOS and Windows installer entries retained the expected commands and selectorsSecurity
Setup commands execute only after the user explicitly invokes
allagents workspace setup. Creating a workspace from a remote template and ordinary synchronization never execute them. Unknown platform/architecture values fail validation; nonmatching entries are skipped before process creation.