Committing the wrong latest changes detected in my projects
Created originally on Bitbucket by plum117
During a day of work with all the possible distractions it happen often that the changes I'm looking at and going to commit are actually not the latest changes since "I forgot" to hit the refresh file list button.
By "forgetting" this button, I often push an older version of my latest changes on the mercurial repo and moreover, I make the bamboo build failed because of missing code (thanks bamboo).
However, I was wondering why tortoisehq : A. Does not sometimes refresh automatically the latest changes in the commit tab or B. Why at least when I'm going to commit, do not warn me that I'm actually not really committing the latest changes.
So, I would suggest on commit to have a warning message when you are committing changes that are actually not the latest one detected in your project with a "Do you want to continue or load latest changes". Also, a checkbox "Do not mentioned again" could be there for those that do not want to be warn like this.
Attachments: 2017-02-20_10-59-47