In Designer, a commit represents a snapshot of your work in your current branch. A commit contains a unique identifier that helps you track changes to your pipelines over time. Performing a commit lets you save your changes and push to your remote repository.
|Branch||This is the checked-out branch where you’ve made changes and intend to capture the snapshot. You can't edit this—you must switch branches to make a commit on another branch.|
|Commit message||A text field to enter a brief description of the changes you’ve made for this commit.|
|Publish pipelines||A toggle to enable publishing of pipelines. Publishing makes pipelines available for scheduling. Any existing schedules will run the updated published pipeline. You can only publish pipelines from the
|Select environment to publish to||If Publish pipelines is toggled on, select the environment that the scheduled pipelines will use. Read Add environment to learn more about environments.|
How to commit
Once you have made changes to your branch, the Git button in the upper-right displays an i icon to indicate that there are changes to commit. Your branch must be up-to-date with any changes from the remote branch before you can commit and push your own changes.
Follow the steps below to commit your changes:
Click Commit in the Git drop-down menu. The Commit changes and push dialog will open.
If your copy of the branch is "behind" the remote branch, you'll be prompted to run Pull remote changes first. Once your copy of the branch is up-to-date, you can continue with the commit.
Add a brief description of the changes you’ve made for this commit so that other collaborators can understand what changes you've made.
- If you want to publish your pipelines to make them available for scheduling, toggle on Publish pipelines. Otherwise, proceed to step 5.
- Select the environment that the scheduled pipelines will use.
- Click Commit to save your snapshot and push these changes to the remote repository. Otherwise, click Cancel to cancel your commit.
If there are no changes since your last commit, the message Unable to commit changes. There are no changes to commit will be displayed at the end of this process.
The Commit action will commit all pipelines in your current branch, preserving the pipeline folder structure. However, it will not commit empty folders; these will disappear from the pipeline list.