feat: allow artifact management and transfer workflows - #75
Merged
Conversation
Chart CI passedRepository hygiene and Helm validation passed. View the workflow run. |
xnoto
force-pushed
the
feat/opencode-artifact-permissions
branch
from
September 3, 2026 20:47
aef6a7c to
f44f83f
Compare
xnoto
changed the title
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.
No repository pull-request template exists.
Summary
/artifactscloud-artifact-transferskill explaining cloud-MCP and Agent-Pipe boundariesValidation
pre-commit run --all-filesSecurity
No
bashpermission is broadened; symlink-resolved external paths outside/artifactsremain rejected. Signed URLs remain bearer capabilities and are never user-facing.