docs: github action and pkg docs (#172)

* docs: github action and pkg docs

* chore: implement requested changes

Author: AstraBert

docs/src/content/docs/llamaagents/llamactl-reference/commands-pkg.md

@@ -0,0 +1,70 @@
+---
+title: pkg
+sidebar:
+  order: 106
+---
+
+:::caution
+This command is currently limited to python **agent workflows**.
+Frontend packaging is **not yet supported**.
+:::
+
+The `pkg` command group lets you package and export your application for custom deployments.
+Currently it supports exporting a Dockerfile that can be built into an image with any OCI compliant image builder, such as `docker` or `podman`.
+
+
+## Usage
+
+```bash
+llamactl pkg [COMMAND] [options]
+```
+
+### Available Commands
+
+- `container` – Generate a minimal, build-ready container file (e.g., `Dockerfile`) for your workflows.
+
+
+## Command: `container`
+
+```bash
+llamactl pkg container [DEPLOYMENT_FILE] [options]
+```
+
+Generates a container build file from a given deployment file and user-specified options.
+
+### Options
+
+
+- `deployment_file` - Path to the deployment file. Defaults to the current directory (`.`)
+- `--python-version` - Python version for the base image. If not specified, it's inferred from `.python-version` or `pyproject.toml`; defaults to **3.12** if none found.
+- `--port <int>` - Port to expose for the API server. Defaults to 4501.
+- `--dockerignore-path` - Path for the generated `.dockerignore` file. Defaults to `.dockerignore`.
+- `--overwrite` - Overwrite any existing output files. No default value.
+- `--exclude <path>` - Path(s) to exclude from the build (appended to `.dockerignore`). Can be used multiple times. No default value.
+- `--output-file` - Path and filename for the generated container build file. Defaults to `Dockerfile`.
+- `--help` - Show help for this command and exit. No default value.
+
+### Notes
+
+- The generated `.dockerignore` file automatically excludes common Python-related directories such as:
+  - Local virtual environments
+  - Caches
+  - Files that may contain sensitive data (e.g., `.env`)
+- The produced container file is **minimal by design**. It should work for most cases, but you may need to customize it for specific use cases.
+
+### Examples
+
+**1. Create default `Dockerfile` and `.dockerignore`:**
+```bash
+llamactl pkg container
+```
+
+**2. Generate a custom container file with specific name, Python version, and port:**
+```bash
+llamactl pkg container --output-file Containerfile --python-version 3.14 --port 4502
+```
+
+**3. Exclude certain files or directories from the build:**
+```bash
+llamactl pkg container --exclude .env.local --exclude .github/workflows/ --exclude "*.pdf"
+```

docs/src/content/docs/llamaagents/llamactl/cd-with-github-actions.md

@@ -0,0 +1,51 @@
+---
+title: Continuous Deployment with GitHub Actions
+sidebar:
+  order: 19
+---
+:::caution
+LlamaAgents is currently in alpha. You can try it out locally or [request access by contacting us](https://landing.llamaindex.ai/llamaagents?utm_source=docs).
+:::
+
+As described in the [Getting Started](/python/cloud/llamaagents/getting-started) guide, deploying a LlamaAgent to LlamaCloud requires connecting it to a `git` source (specifically, GitHub).
+
+However, when you push changes to GitHub, they are not automatically applied to your LlamaAgent. To keep your deployment in sync with your `git` reference, you must manually run `llamactl deployments update`.
+
+This manual approach provides fine-grained control over when changes to your production branch are deployed, but it may not fit every workflow.
+
+If you prefer to automate the process using continuous deployment, you can use the `run-llama/llamactl-deploy` GitHub Action.
+
+To use this action, you’ll need:
+
+- A LlamaCloud API key
+- The Project ID associated with your LlamaAgent deployment
+- The ID of the deployed LlamaAgent
+
+Optionally, you can specify a `git` reference for the deployment (such as a commit SHA or branch name).
+
+Here’s an example workflow configuration:
+
+```yaml
+name: Update LlamaAgent Deployment
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  update-deployment:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Update deployment
+        uses: run-llama/[email protected]
+        with:
+          llama-cloud-api-key: ${{ secrets.LLAMA_CLOUD_API_KEY }}
+          llama-cloud-project-id: ${{ secrets.LLAMA_CLOUD_PROJECT_ID }}
+          deployment-id: "your-deployment-id"
+          git-reference: ${{ github.sha }} # optional
+```
+
+You can find the reference for this GitHub Action in the [dedicated repository](https://github.com/run-llama/llamactl-deploy).

docs/src/content/docs/llamaagents/llamactl/getting-started.md

@@ -131,7 +131,13 @@ When you save, LlamaAgents will verify that it has access to your repository (an
 After creation, the TUI will show deployment status and logs.
 - You can later use `llamactl deployments get` to view again.
 - You can add secrets or change branches with `llamactl deployments edit`.
-- If you update your source repo, run `llamactl deployments update` to roll a new version.
+- If you update your source repo, run `llamactl deployments update` to roll a new version. If you are interested in automating the deployment updates with GitHub Actions, you can read the [Continuous Deployment guide](/python/cloud/llamaagents/cd-with-github-actions)
+
+## Alternative Ways to Deploy
+
+If you prefer a self-hosted deployments, `llamactl` has utilities to export your workflows to container files, so that you can easily build images and deploy your agent workflow anywhere.
+
+Read more about this in the [`pkg` command reference](/python/cloud/llamaagents/llamactl-reference/commands-pkg).
 
 ---