Commit Template

Argument	Description
`<slug>`	The slug of the template to commit (required)

Argument

Description

<slug>

The slug of the template to commit (required)

Flag	Description	Default
`-h, --help`	Show help for the command	–
`-m, --commit-message string`	Message describing the changes in this commit	–
`-f, --force`	Force commit by skipping variants with errors	–

Flag

Description

Default

-h, --help

Show help for the command

–

-m, --commit-message string

Message describing the changes in this commit

–

-f, --force

Force commit by skipping variants with errors

–

Example

# Commit a template in the staging workspace
suprsend template commit order-shipped

# Commit with a message
suprsend template commit order-shipped --commit-message "Fix Hindi variant subject line"

# Commit in production
suprsend template commit order-shipped --workspace production

# Commit in production, skipping variants with errors
suprsend template commit order-shipped --workspace production --force

End-to-End Example

# 1. Pull the current live version to local files
suprsend template pull --slug order-shipped

# 2. Edit the local template file
#    (update variant content, conditions, mock data, etc.)

# 3. Push the edited file as a draft
suprsend template push --slug order-shipped

# 4. Commit the draft to make it live
suprsend template commit order-shipped --commit-message "Add Hindi variant"

Or collapse push and commit into one step:

suprsend template push --slug order-shipped --commit --commit-message "Add Hindi variant"

Using --force skips validation on variants that have errors and commits the rest. Variants with errors remain in draft. Use with caution in production workspaces.

Getting Started with CLI

Updates and Versioning

Sync

Workflow

Template

Schema

Event

Preference Category

Translation

Syntax

Arguments

Flags

Example

End-to-End Example

​Syntax

​Arguments

​Flags

​Example

​End-to-End Example

Syntax

Arguments

Flags

Example

End-to-End Example