Dear @SamKirkland
Thanks for your tool. We are using your FTP-Deploy-Action to deploy our local repository to an FTP server. However, we have encountered an issue during the initial deployment.
When deploying for the first time, the action updates all files on the FTP server, even though only a few files have changed locally and been committed to the GitHub repository. This causes unnecessary updates and potential issues with our live site.
We would like to request a configuration option that allows us to prevent the full FTP sync on the first run. Instead, we would like the action to only update the files that have been changed locally and committed to the repository. This would ensure a more efficient and safe deployment process.
Please let us know if this is something you can implement or if there's a workaround available. Thank you for your time and assistance!
Dear @SamKirkland Thanks for your tool. We are using your FTP-Deploy-Action to deploy our local repository to an FTP server. However, we have encountered an issue during the initial deployment. When deploying for the first time, the action updates all files on the FTP server, even though only a few files have changed locally and been committed to the GitHub repository. This causes unnecessary updates and potential issues with our live site. We would like to request a configuration option that allows us to prevent the full FTP sync on the first run. Instead, we would like the action to only update the files that have been changed locally and committed to the repository. This would ensure a more efficient and safe deployment process. Please let us know if this is something you can implement or if there's a workaround available. Thank you for your time and assistance!