Problem:

Currently, when deploying applications using a GitHub repository, any change within the repository triggers a deployment, even if those changes are unrelated to the deployed application. For example, when setting up an application deployment, users provide the repository link, branch, and source directory (e.g., ./server). While the system builds and deploys only the specified directory, changes in any other directory (e.g., ./client) or in files like README.md still trigger an auto-deploy.

Proposed Solution:

Implement a "build filter" feature that allows users to configure their deployment pipelines to ignore changes in specific paths within a repository. This would prevent unnecessary deployments when changes are made to files or directories that are not relevant to the deployed application.

Attached is an example from another service illustrating a similar feature.