Repository navigation
feat: add direct source deploy capability - #103
Merged
Merged
Conversation
teckedd-code2save
marked this pull request as ready for review
September 21, 2026 02:24
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.
Adds a secret-safe MCP source deploy path that syncs a linked GitHub repository using short-lived GitHub App credentials, builds on the target VPS, recreates the Compose workload, and verifies it without GitHub Actions. Also shortens MCP tool-catalog cache and publishes a toolset revision so new capabilities such as deployment.config.check are rediscovered faster.