@clawcipes/recipes 0.2.6 → 0.2.7
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/package.json
CHANGED
|
@@ -317,6 +317,32 @@ templates:
|
|
|
317
317
|
4) If it fails:
|
|
318
318
|
- Move the ticket back to `work/in-progress/` and assign to the right owner.
|
|
319
319
|
|
|
320
|
+
## Cleanup after testing
|
|
321
|
+
|
|
322
|
+
If your test involved creating temporary resources (e.g., scaffolding test teams, creating test workspaces), **clean them up** after verification:
|
|
323
|
+
|
|
324
|
+
1) Remove test workspaces:
|
|
325
|
+
```bash
|
|
326
|
+
rm -rf ~/.openclaw/workspace-<test-team-id>
|
|
327
|
+
```
|
|
328
|
+
|
|
329
|
+
2) Remove test agents from config (agents whose id starts with the test team id):
|
|
330
|
+
- Edit `~/.openclaw/openclaw.json` and remove entries from `agents.list[]`
|
|
331
|
+
- Or wait for `openclaw recipes remove-team` (once available)
|
|
332
|
+
|
|
333
|
+
3) Remove any cron jobs created for the test team:
|
|
334
|
+
```bash
|
|
335
|
+
openclaw cron list --all --json | grep "<test-team-id>"
|
|
336
|
+
openclaw cron remove <jobId>
|
|
337
|
+
```
|
|
338
|
+
|
|
339
|
+
4) Restart the gateway if you modified config:
|
|
340
|
+
```bash
|
|
341
|
+
openclaw gateway restart
|
|
342
|
+
```
|
|
343
|
+
|
|
344
|
+
**Naming convention:** When scaffolding test teams, use a prefix like `qa-<ticketNum>-` (e.g., `qa-0017-social-team`) so cleanup is easier.
|
|
345
|
+
|
|
320
346
|
test.tools: |
|
|
321
347
|
# TOOLS.md
|
|
322
348
|
|
|
@@ -170,6 +170,32 @@ templates:
|
|
|
170
170
|
Output conventions:
|
|
171
171
|
- Test plans (optional) go in work/test-plans/
|
|
172
172
|
|
|
173
|
+
## Cleanup after testing
|
|
174
|
+
|
|
175
|
+
If your test involved creating temporary resources (e.g., scaffolding test teams, creating test workspaces), **clean them up** after verification:
|
|
176
|
+
|
|
177
|
+
1) Remove test workspaces:
|
|
178
|
+
```bash
|
|
179
|
+
rm -rf ~/.openclaw/workspace-<test-team-id>
|
|
180
|
+
```
|
|
181
|
+
|
|
182
|
+
2) Remove test agents from config (agents whose id starts with the test team id):
|
|
183
|
+
- Edit `~/.openclaw/openclaw.json` and remove entries from `agents.list[]`
|
|
184
|
+
- Or wait for `openclaw recipes remove-team` (once available)
|
|
185
|
+
|
|
186
|
+
3) Remove any cron jobs created for the test team:
|
|
187
|
+
```bash
|
|
188
|
+
openclaw cron list --all --json | grep "<test-team-id>"
|
|
189
|
+
openclaw cron remove <jobId>
|
|
190
|
+
```
|
|
191
|
+
|
|
192
|
+
4) Restart the gateway if you modified config:
|
|
193
|
+
```bash
|
|
194
|
+
openclaw gateway restart
|
|
195
|
+
```
|
|
196
|
+
|
|
197
|
+
**Naming convention:** When scaffolding test teams, use a prefix like `qa-<ticketNum>-` (e.g., `qa-0017-social-team`) so cleanup is easier.
|
|
198
|
+
|
|
173
199
|
lead.tools: |
|
|
174
200
|
# TOOLS.md
|
|
175
201
|
|