@action-llama/action-llama 0.1.4 → 0.1.5
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +27 -1
- package/dist/cli/commands/new.js +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -56,7 +56,7 @@ Once setup finishes:
|
|
|
56
56
|
|
|
57
57
|
```bash
|
|
58
58
|
cd my-project
|
|
59
|
-
al start
|
|
59
|
+
npx al start # if using local install
|
|
60
60
|
```
|
|
61
61
|
|
|
62
62
|
The dev agent will poll every 5 minutes looking for issues that match its filter: the issue must have the trigger label (default: `agent`) **and** be assigned to the configured user. When it finds a match, it clones the repo, creates a branch, implements the changes described in the issue, runs tests, and opens a PR.
|
|
@@ -80,6 +80,8 @@ Credentials are stored separately in `~/.action-llama-credentials/` (shared acro
|
|
|
80
80
|
|
|
81
81
|
## CLI commands
|
|
82
82
|
|
|
83
|
+
If you installed globally (`npm install -g @action-llama/action-llama`), you can use `al` directly. Otherwise, prefix commands with `npx` (e.g., `npx al start`).
|
|
84
|
+
|
|
83
85
|
| Command | Description |
|
|
84
86
|
|---------|-------------|
|
|
85
87
|
| `al new <name>` | Create a new project (interactive setup for credentials, model, and agents) |
|
|
@@ -164,6 +166,30 @@ To use webhooks instead of polling, enable them during `al new` and add a webhoo
|
|
|
164
166
|
|
|
165
167
|
Payloads are validated with HMAC-SHA256 (`x-hub-signature-256`). Webhook filters in `webhooks.filters` support matching on `source`, `repos`, `events`, `actions`, `labels`, `assignee`, `author`, and `branches` (AND logic; omitted fields are not checked).
|
|
166
168
|
|
|
169
|
+
#### Local development with ngrok
|
|
170
|
+
|
|
171
|
+
If you're developing locally and need GitHub to reach your machine, use [ngrok](https://ngrok.com) to create a public tunnel:
|
|
172
|
+
|
|
173
|
+
```bash
|
|
174
|
+
# Install ngrok (macOS)
|
|
175
|
+
brew install ngrok
|
|
176
|
+
|
|
177
|
+
# Start a tunnel pointing at the Action Llama gateway port
|
|
178
|
+
ngrok http 8080
|
|
179
|
+
```
|
|
180
|
+
|
|
181
|
+
ngrok will print a forwarding URL like `https://a1b2c3d4.ngrok-free.app`. Use that as your GitHub webhook Payload URL:
|
|
182
|
+
|
|
183
|
+
```
|
|
184
|
+
https://a1b2c3d4.ngrok-free.app/webhooks/github
|
|
185
|
+
```
|
|
186
|
+
|
|
187
|
+
Keep the ngrok process running alongside `al start`. The tunnel stays active until you stop it. For a stable URL across restarts, sign up for a free ngrok account and use a static domain:
|
|
188
|
+
|
|
189
|
+
```bash
|
|
190
|
+
ngrok http 8080 --url=your-name.ngrok-free.app
|
|
191
|
+
```
|
|
192
|
+
|
|
167
193
|
### Docker mode
|
|
168
194
|
|
|
169
195
|
Set `"docker": { "enabled": true }` in `config.json`. Agents run in isolated containers with credentials mounted read-only at `/credentials/`, a read-only root FS, dropped capabilities, non-root user, and PID/memory/CPU limits. Each container gets a unique shutdown secret for the anti-exfiltration kill switch. The Docker image is built automatically on first run from `docker/Dockerfile`.
|
package/dist/cli/commands/new.js
CHANGED