Repository navigation
feat(docs): add github app deployment option - #298
Conversation
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
| void github join | ||
| ``` | ||
|
|
||
| ::: 3. Link your repository to your project |
There was a problem hiding this comment.
Markdown syntax error: The closing ::: tag for the details block is incorrectly combined with step 3's header on the same line. This will cause the details block to not close properly and step 3 to be malformed.
The line should be split:
:::
3. Link your repository to your project| ::: 3. Link your repository to your project | |
| ::: | |
| 3. Link your repository to your project | |
Spotted by Graphite
Is this helpful? React 👍 or 👎 to let us know.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a6934b73bb
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| void github join | ||
| ``` | ||
|
|
||
| ::: 3. Link your repository to your project |
There was a problem hiding this comment.
The closing marker must be ::: on its own line. With 3. Link your repository... appended to it, VitePress does not close the details container, so steps 3–6 and the subsequent GitHub Actions and Other Targets sections are rendered inside the collapsed “someone already installed the App” block.
Useful? React with 👍 / 👎.
| 6. Follow the build | ||
|
|
||
| ```bash | ||
| void build logs --follow |
There was a problem hiding this comment.
When the GitHub webhook has not created the new build by the time this command runs, runBuildLogsCommand selects the newest existing build only once (packages/void/src/cli/build-cmd.ts, lines 123–132). Following these consecutive steps can therefore show a previous completed build—or exit with “No builds found”—rather than follow the push from step 5; the instructions should wait until the new build appears or identify that build explicitly.
Useful? React with 👍 / 👎.
Documents github app deployment