Synopsis
Arguments
| Name | Type | Required | Description |
|---|---|---|---|
slug | string | yes | The agent’s slug. |
repo | string | yes | Repository display name (e.g. org/repo). |
strategy | string | yes | One of merge, rebase, or none. See Strategies below. |
--workspace | string | no | Workspace name. Overrides the value from murmur.yaml. |
Strategies
| Value | Behavior |
|---|---|
merge | Merge the base branch into the working branch on file changes. |
rebase | Rebase the working branch onto the base branch on file changes. |
none | Suppress file-changed notifications for this repo entirely. |
Examples
Switch a repo to rebase
Silence file-changed notifications on a noisy repo
acme/docs but no longer receives notifications when the base branch advances.
Errors
| Code | Meaning | What to do |
|---|---|---|
NOT_FOUND | No agent with that slug exists, or the repo is not attached to the agent. | Use murmur ls and murmur status to verify the slug and the agent’s repos. |
UNAUTHENTICATED | Identity token is missing or expired. | Run murmur auth or check your murmur.local.yaml configuration. |
invalid strategy | The strategy value is not merge, rebase, or none. | Pass one of the supported strategies listed above. |
Related
- Agents — concept overview
murmur queue add— send a follow-up to an agentmurmur queue clear— discard all queued follow-upsmurmur queue strategy— set how follow-ups are drainedmurmur subscriptions add— subscribe to branch/file events