All Collections
Troubleshooting
Fixing errors when pulling commits into a deployment
Fixing errors when pulling commits into a deployment
Lior Neudorfer avatar
Written by Lior Neudorfer
Updated over a week ago

When editing a deployment using external tools, you may accidentally commit NACL files which contain some errors. Salto will detect these when pulling the commits into the deployment, and will show this error screen:

In this screen, users can review which files contain errors, and in which lines.

To fix these problems, users have 3 options:

Solution 1: Committing and pushing fixes

Using the same editing method that was used to do the initial edits (either your own IDE, or a Web Editor), review your NACL files and fix the indicated syntax problems. Once done, commit and push your fixes to the same Pull Request "after" branch. Salto will then detect these new changes and prompt the user to pull them into the deployment.

Solution 2: Reverting your commits

Using the same editing method that was used to do the initial edits (either your own IDE, or a Web Editor), select a previous git commit that did not contain any errors, and perform a "git revert" action to that commit. Git will then generate new commits, overriding your invalid edits and returning the branch to an error-less state. Then, push these commits to the Pull Request's "after" branch. Salto will detect these new changes and prompt the user to pull them into the deployment.

Solution 3: Reverting to a previously valid deployment

In case the user had a valid Deployment Preview before doing the invalid edits, Salto can automatically revert to it. To do this:

  1. View the last valid deployment preview, using the 3 dots menu:
    โ€‹

  2. Click the "Revert to This Deployment" button in the top right corner

Did this answer your question?