hugocasa 29f5880809 fix(forks): always clone triggers/schedules disabled, drop opt-in flag ...

Disabled triggers and schedules are inert — no listener attaches, no cron
fires — so cloning them by default is safe by construction. Drops the
fork_triggers opt-in flag introduced earlier in this PR:

- Drops workspace.fork_triggers column (migration removed)
- Removes fork_triggers from CreateWorkspaceFork (API + OpenAPI)
- Removes the conditional in create_workspace_fork — clone always runs
- Removes the toggle from the fork-creation dialog
- Removes --fork-triggers from `wmill workspace fork`
- Updates docs/fork-triggers.md and adding-a-trigger SKILL.md

The merge UI continues to exclude triggers from the deploy/update default
selection, so a routine merge from a fork doesn't accidentally push
trigger config the user hasn't intentionally changed.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-30 17:29:03 +02:00

..

commands

fix(forks): always clone triggers/schedules disabled, drop opt-in flag

2026-04-30 17:29:03 +02:00

core

feat(cli): wmill dev with per-flow proxy and responsive Dev UI (#8529)

2026-04-27 20:14:21 +00:00

guidance

fix: split flow prompts for frontend chat (#8968)

2026-04-29 14:56:51 +00:00

utils

feat(cli): wmill dev with per-flow proxy and responsive Dev UI (#8529)

2026-04-27 20:14:21 +00:00

main.ts

chore(main): release 1.692.0 (#8950)

2026-04-27 20:22:48 +00:00

types.ts

feat: add Azure Event Grid triggers (#8888)

2026-04-23 16:30:18 +00:00