Several clients have expressed the need for greater flexibility in deploying Git repositories, specifically the ability to define a custom file path for deployment. The latest request from a partner emphasizes the importance of this feature:
* Define a custom file path for deployment
"It would be beneficial if we could specify a deploy point within the file system. For instance, we typically populate our repository one level above the 'public/' directory."
Currently, the Servebolt Git integration deploys all files directly into the 'public/' directory.