After identifying the file that caused a regression in my code, I searched for it in SM to try to find the commit that brought caused the issue. However, I couldn’t find any commit whose diff shows the introduction of the bug. I was only able to find the issue by traversing all of the commits on the repo without the search function filtering out the commits affecting other files.
In trying to figure out why I wasn’t seeing the merge-commit that caused the regression in the search, I stumbled upon the max-parents setting that helped me find that merge-commit in the search by setting it to max-parents:2 in the search query.
This raised 2 questions:
- Why is the default max-parents setting set to 1? Combined with the search showing all commits as being linear in the graph (ignoring branching), this causes what I believe to be a UX issue, giving a false sense to the user that he’s seeing all commits that affected the particular file when it’s not the case.
- Is there a way to set the default max-parents to 2 in the settings?