@ludeo/cli 1.4.11 → 1.4.13

package/README.md

@@ -114,6 +114,8 @@ ludeo builds upload \
 - `--request-id`: Optional request ID for tracking
 - `--no-interactive`: Disable interactive prompts (for CI/CD or scripts)
 - `--dry-run`: Preview the upload without making any changes
+- `--poll`: After upload completes, poll build status until it leaves pending state
+- `--interval N`: Polling interval in seconds when using `--poll` (default: 10)
 
 #### Dry-Run Mode
 Preview what would be uploaded without making any changes:
@@ -133,7 +135,39 @@ Dry-run will:
 - Show total file count and size
 - NOT create any build metadata or upload files
 
-### 4. Manage Builds
+### 4. Check Build Status
+
+After uploading you can check whether the platform has finished processing a build:
+
+```bash
+# Single check — prints current status and exits
+ludeo builds status --game-id YOUR_GAME_ID --build-id BUILD_ID
+
+# Poll until the build leaves the pending state (useful in CI/CD)
+ludeo builds status --game-id YOUR_GAME_ID --build-id BUILD_ID --poll
+
+# Poll with a custom interval (default is 10 s)
+ludeo builds status --game-id YOUR_GAME_ID --build-id BUILD_ID --poll --interval 5
+```
+
+`--poll` continues while the status is `pending` and exits as soon as it changes:
+- Exit 0 — status is `ready`, `success`, or `complete`
+- Exit 1 — any other status (e.g. `failed`)
+
+You can also trigger polling automatically right after an upload:
+
+```bash
+ludeo builds upload \
+  --game-id YOUR_GAME_ID \
+  --exec-path game.exe \
+  --local-directory ./builds \
+  --build-type major \
+  --game-version "1.2.3" \
+  --sdk-version "2.0.0" \
+  --poll
+```
+
+### 5. Manage Builds
 ```bash
 # List your builds
 ludeo builds list --game-id YOUR_GAME_ID
@@ -148,10 +182,40 @@ ludeo auth status
 ludeo auth logout
 ```
 
+## Project Config (`ludeo.json`)
+
+To avoid repeating the same flags on every command, you can store per-project defaults in a `ludeo.json` file in your project directory (or any ancestor directory up to `$HOME`).
+
+Scaffold a template:
+```bash
+ludeo config init
+```
+
+This creates a `ludeo.json` with all supported fields. Fill in the values you want to persist:
+
+```json
+{
+  "game_id": "YOUR_GAME_ID",
+  "exec_path": "game.exe",
+  "local_directory": "./builds",
+  "build_type": "major",
+  "sdk_version": "2.0.0"
+}
+```
+
+Once the file is in place, you can upload with just:
+```bash
+ludeo builds upload --game-version "1.2.3"
+```
+
+Flag values always override the project config, which overrides global defaults. Use `--project-config <path>` to point to a config file in a non-standard location.
+
 ## Features
 
 - **Interactive Mode**: Guided wizard for easy build uploads - just run `ludeo builds upload` and follow the prompts
 - **Easy Upload**: Upload complete game builds with a single command
+- **Build Status Polling**: Check and poll build processing status with `builds status --poll`; also available directly on `builds upload --poll`
+- **Project Config**: Store per-project defaults in `ludeo.json` via `ludeo config init` — no more repeating the same flags
 - **Large File Support**: Automatically handles large files and multiple files
 - **Progress Tracking**: Real-time progress updates during uploads
 - **Dry-Run Mode**: Preview uploads without making changes using `--dry-run`
@@ -173,7 +237,7 @@ npm update -g @ludeo/cli
 - name: Install Ludeo CLI
   run: npm install -g @ludeo/cli
 
-- name: Upload Build
+- name: Upload Build and Wait for Processing
   run: |
     ludeo auth set-token --access-token ${{ secrets.LUDEO_ACCESS_TOKEN }}
     ludeo builds upload \
@@ -183,7 +247,30 @@ npm update -g @ludeo/cli
       --build-creation-type new \
       --build-type major \
       --game-version ${{ env.GAME_VERSION }} \
+      --sdk-version ${{ env.SDK_VERSION }} \
+      --poll
+```
+
+If you prefer to separate the upload and status-check steps:
+```yaml
+- name: Upload Build
+  id: upload
+  run: |
+    ludeo auth set-token --access-token ${{ secrets.LUDEO_ACCESS_TOKEN }}
+    ludeo builds upload \
+      --game-id ${{ env.GAME_ID }} \
+      --exec-path game.exe \
+      --local-directory ./builds \
+      --build-type major \
+      --game-version ${{ env.GAME_VERSION }} \
       --sdk-version ${{ env.SDK_VERSION }}
+
+- name: Wait for Build to Be Ready
+  run: |
+    ludeo builds status \
+      --game-id ${{ env.GAME_ID }} \
+      --build-id ${{ env.BUILD_ID }} \
+      --poll --interval 15
 ```
 
 ## Troubleshooting

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ludeo/cli",
-  "version": "1.4.11",
+  "version": "1.4.13",
   "description": "Ludeo CLI - Upload game builds and manage content on the Ludeo platform",
   "main": "index.js",
   "bin": {

package/scripts/pre-commit

@@ -0,0 +1,26 @@
+#!/bin/sh
+# Pre-commit hook: ensures README.md and windows-releases/template/README.md
+# are always generated from docs/README.template.md and never edited directly.
+#
+# Install: make install-hooks
+
+README_FILES="README.md windows-releases/template/README.md"
+
+# Only run if the template or any generated README is being committed
+TEMPLATE_STAGED=$(git diff --cached --name-only | grep -q "docs/README.template.md" && echo "yes" || echo "no")
+READMES_STAGED=$(git diff --cached --name-only | grep -E "^README\.md$|^windows-releases/template/README\.md$" && echo "yes" || echo "no")
+
+if [ "$READMES_STAGED" = "yes" ] && [ "$TEMPLATE_STAGED" = "no" ]; then
+  echo "❌ README files cannot be edited directly."
+  echo "   Edit docs/README.template.md and run 'make readme' to regenerate."
+  exit 1
+fi
+
+if [ "$TEMPLATE_STAGED" = "yes" ]; then
+  # Template is being committed — regenerate and auto-stage the outputs
+  node scripts/build-readme.js
+  git add $README_FILES
+  echo "✅ README files regenerated from template and staged"
+fi
+
+exit 0