This issue has been raised earlier, but the 'resolution' to that issue was not good, or at least, should have been optional.

I am not sure how people are tackling this issue in general but if I have a 'dev' and 'default' branches, the branches mostly accept merges as programmers work in different branches then merge them into dev. When the dev compiles and is tested, it is merged into default. We absolutely need the dev/default to start building as soon as there is a merge.

This was disabled when someone raised the issue that there were un-necessary builds. I'd rather have un-necessary builds telling me 'Successful!' than no builds at all.

At the very least, there should be a compromise. The following command is executed every-time the plugin polls the repository:

$ hg log --style <repository path>\tmp4601530738732108532style --branch dev --no-merges --prune

I would like the option to remove `--no-merges` from it. Please expose this so that we can optionally change it. Currently, this is becoming a big issue so much so that we may have to switch from Jenkins.

I would really appreciate resolution of this issue. Thank you.