Skip to main content
All CollectionsIntegrating Git and CI/CD
Manually Pushing Environment Changes
Manually Pushing Environment Changes
Support avatar
Written by Support
Updated over a week ago

When automatic push mode is not enabled, a counter representing the amount of un-pushed files will appear on the Git widget in the environment header

Clicking on the Git widget will allow you to preview and push all or some of those un-pushed files. Clicking on ‘Preview Push’ will take you to a screen allowing you to review your un-pushed files, their changes as well as selecting files your would like to push, provide a git message and push.

You can select one or more files or all of them via the ‘Select All’ CTA at the bottom. In some business applications, you can also use the Changed By and Changed At filters to quickly find recent changes, or changes made by a specific user. This can help you find the latest changes made by you or other users.

On the right side you can document the nature of the change via the title and message boxes. Selecting at least one file and adding a title enables the ‘Push’ button. Clicking the button will commit your message, along with the code change to Git.

Make sure to mention your ticket number, e.g., in Jira that would be your project name and the ticket number: name-3754, so that your comment and link to the code change in Git will appear in the relevant ticket in your ticketing system.

To enforce a specific Git commit message pattern, such as requiring a mention of a Jira ticket, please refer to the commit message patterns page

You can mention multiple tickets within one Push event if your code change addressed multiple tickets. Similarly you can select multiple files with one ticket and Push event, if your ticket was addressed by changes in multiple files.

Salto supports Jira ‘Smart Commits’. This feature allows actions such as commenting on or closing a ticket in Jira, directly from Salto. Enabling this feature in Jira also allows you to automatically add a list of all of your documented file names by adding {{fileNames}} to your commit message.

Manually Pushing Salto Deployed Changes

When the automatic push mode for Salto deployments is disabled, a push button will be displayed on the deployment summary screen, enabling you to push only the file changes relevant to that deployment.

The git commit message will automatically include all pertinent deployment details, along with a comprehensive list of all impacted NACL files.

Hiding Files and Folders

In some cases, you may want to only document changes to a specific set of files - for example, if you have sensitive configuration elements, and you only wish to document changes to them.

In this case, Salto supports hiding elements that you do not wish to document from the "Preview Push" screen.

To do this, click the "..." menu next to a folder or a file you wish to hide, and select Hide File.

Once hidden, the selected files and folders won't show up by default in the Preview Push file-tree. You can still see them by opening the "Hidden Files" menu and toggling the "Show Hidden Files" option.

Note that only environment owners and administrators can add or remove hidden files.

Did this answer your question?