> For the complete documentation index, see [llms.txt](https://disdat.gitbook.io/disdat-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://disdat.gitbook.io/disdat-documentation/reference/dsdt-the-cli/dsdt-commit.md).

# dsdt commit

### Description

Your local context keeps every version of your bundle.   But only committed bundles may be pushed to a remote context.     

### Usage

```bash
usage: dsdt commit [-h] [-u UUID] [-t TAG] [bundle]
```

### Options

```bash
positional arguments:
  bundle                Bundle name to commit in the current context
                        (optional)

optional arguments:
  -h, --help            show this help message and exit
  -u UUID, --uuid UUID  Bundle UUID to commit
  -t TAG, --tag TAG     Having a specific tag: 'dsdt rm -t committed:True -t
                        version:0.7.1'
```

### Examples

Commit the `bonkers` bundle.  Print out the meta data, and see that `COMMITTED` is `True`. 

```bash
$ dsdt commit bonkers
$ dsdt ls -v bonkers
NAME                	PROC_NAME           	OWNER   	DATE              	COMMITTED	UUID                                    	TAGS
bonkers             	BundleWrapperTask_bonkers_6da4eb3137	kyocum  	03-04-20 17:08:23 	True    	251f6402-90ce-4393-80bc-959f68a1baab

```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://disdat.gitbook.io/disdat-documentation/reference/dsdt-the-cli/dsdt-commit.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.