Open
Conversation
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
paulleseute
reviewed
Feb 7, 2026
Contributor
paulleseute
left a comment
paulleseute
left a comment
There was a problem hiding this comment.
I think we should have a unique path for deployment. From what I understand users have to go log on Alpic in both cases, so we should choose wether we want them to link a repo or upload the code.
| ## Deploy | ||
|
|
||
| - **Ship to production** → [deploy.md](references/deploy.md): when ready to deploy via Alpic | ||
| - **Ship to production** → [deploy.md](references/deploy.md): when ready to deploy via Alpic. Use the **Alpic CLI** (`npx alpic deploy`) for CLI-based deploy, or the dashboard for GitHub-based deploy. |
Contributor
There was a problem hiding this comment.
I think we should not mention the CLI now because it lower the chances of the LLM to read the actual deploy doc.
Comment on lines
+3
to
+7
| **Option A — Alpic CLI:** Get an API key from **Team settings** in the [Alpic dashboard](https://app.alpic.ai), set `ALPIC_API_KEY` in the environment, then run `npx alpic deploy` from the project root (or `npx alpic deploy ./path`). On first run the CLI will prompt to create a new project or link to an existing one; the choice is saved in `.alpic/project.json` for future deploys. | ||
|
|
||
| Guide user through these steps: | ||
| **Option B — Dashboard (GitHub):** Push code to a GitHub repo, then deploy via Alpic. | ||
|
|
||
| Guide user through these steps for the dashboard flow: |
Contributor
There was a problem hiding this comment.
We need to distinct which steps should be done by the user, and which one are to be run by the LLM. Also the deploy instructions are likely for first time user, I wonder if having 2 paths is not bringing confusion.
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
2 participants
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 deployment instructions across multiple skills documentation.
chatgpt-app-builder,mcp-app-builder, andskybridgeskills documentation.Greptile Overview
Greptile Summary
Enhanced deployment documentation across three skills (
chatgpt-app-builder,mcp-app-builder, andskybridge) by adding Alpic CLI deployment instructions alongside the existing dashboard-based GitHub deployment method.Key changes:
.alpic/project.jsonThe changes are documentation-only and provide developers with clearer deployment options without modifying any functional code.
Confidence Score: 5/5