✅ Deploy flow: wired pipeline_commit to send repoFullName + YAML from… #19
Conversation
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
… dashboard to backend
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.
This PR updates the deployment flow so the frontend correctly passes repoFullName, yaml, and other contextual fields from the Dashboard to the backend’s /mcp/v1/pipeline_commit endpoint.
✅ Changes
• Refactored startDeploy() in api.ts to include full payload (repoFullName, branch, env, yaml, provider, path).
• Updated useDeployStore.ts to forward the dashboard payload directly.
• Fixed missing usePipelineStore reference by importing the store directly.
• Verified full YAML is now committed to GitHub successfully.
🧠 Context
Previously, only partial payload data (branch, env, provider, path) was being sent, causing 400 errors from the backend (repoFullName and yaml are required). This update resolves that and ensures full commit data alignment between frontend and backend.
🧪 Testing
• Triggered deployment from Dashboard ✅
• Verified full payload in network logs ✅
• Confirmed successful YAML commit to GitHub ✅