# Commit plugin If [editable on the platform](https://docs.flightwatching.com/user-manual/general-conf/configuration/plugins#add-plugin) - commit in order to save the changes in the Version Controlled System. In order to commit plugin(s), the good practice is to check what was changed on the server. The first thing to do is to click on the button CHECK UPGRADES (the button changes into CHECK IN PROGRESS) and wait until the check is finished:

{% hint style="info" %} NOTE: The plugins that can be committed on the platform are the ones that are *editable* on the platform (no lock icon) and that have the *icon* beside its name - *locally edited*. {% endhint %} For example, the plugin *fw\.a320 below* does not have the lock icon, but it does the icon for locally edited:

Click on *DET* button situated on the right side of the line to enter to the details of that plugins:

The details of the plugin was explained previously - [here](https://docs.flightwatching.com/user-manual/admin-user-manual/edit-plugins/..#details-of-plugin). The display of the plugin that is locally edited changes from the 'up-to-date' plugin though (see image above). Here, the new button shows up at the header: ***COMMIT*** and the buttons ***Filter only local changes*** next to some of the elements. When clicking on ***Filter only local changes***, the parts of that element will open and show only what was locally modified. For example, clicking on the ***Filter only local changes*** button beside the *10 dashboards* will open dashboards elements:

To see exactly what was changed click on the ***MODIFY*** button located on the right side of the element:

MODIFY - differences between ref and local

In that example, only modification was the name of the dashboard. Once you have confirmed all the modifications are correct and could be saved to the VCS and could become the new reference, click on ***COMMIT*** button. It will publish the local changes as the new reference. After clicking ***COMMIT*** button, the little window pops up where you **need to** input the reason of commit (that will save that information to the logs):

After clicking on ***OK*** button below the reason of commit, the plugin will start the process of publishing the local changes. The light blue banner shows up with the information: "*INFO: plugin fw\.a320 is being committed. Wait for completion*":

Once the plugin is all set, the banner changes and shows information about the version control with SHA code:

The page auto-refresh after that, and the newly committed plugin is 'clear' from the local modifications:

Let's now [deploy that plugin](https://docs.flightwatching.com/user-manual/admin-user-manual/edit-plugins/deploy-plugin) on another server.