Log in to your harness - The Modern Software Delivery Platform® account to give feedback

Feature Requests

Anonymous

Feature Requests for Harness. Select 'Category' based on the module you are requesting the feature for.
Support for Ignoring Merge Commit Changes in File-Based Triggers
Customers using file-based triggers in Harness CI have observed that pipelines are being executed when a pull request is merged, even if the target directory (e.g., flutter/) was not directly modified in the merge commit itself. The root cause appears to be that GitHub includes all files changed in the source branch when a merge commit is created. Harness currently evaluates the changedFiles condition against this expanded list of files, causing the trigger to fire even if the actual merge did not change the target directory. Current Behavior: Triggers with a condition such as changedFiles: flutter/.* will run if those files were changed at any point in the source branch, even if the final merge commit doesn’t modify them. There is no built-in way to detect merge commits at the trigger level and apply different logic. Requested Enhancement: Introduce support for detecting and optionally ignoring merge commits in trigger evaluations. This could take the form of: A new trigger condition (e.g., isMergeCommit: false) The ability to evaluate only the files changed in the actual merge commit, not in the full history of the source branch A toggle or flag in the trigger UI/API to exclude changes from merge commits Workaround (Currently Required): Users must add a pipeline step to manually inspect the commit metadata and skip execution if it’s a merge commit: a non-ideal solution for CI/CD automation. Impact: This enhancement would prevent unnecessary pipeline runs, reduce execution overhead, and provide more precise control over file-based triggers, especially in monorepos and enterprise-scale workflows.
0
Load More