We're using TFS as our repository. At some point, someone accidentally checked in (via SQL Source Control) a bogus copy of a stored procedure.
Instead of reverting the script/object in SSMS, I used the TFS "rollback changeset" feature to roll back the checkin on the stored procedure's file in the source control tree.
Now I have made a change to that stored procedure and when I try to commit the change, SQL Source Control errors out telling me that there are conflicts which must be resolved. However, there are no conflicts listed in the Get Latest tab and, conceptually, there isn't a conflict in place.
To fix the problem, I used TFS to check-out the stored procedure's script file, edited the script file, checked it back in (again via TFS), and then the object no longer appears on the Commit Changes tab.
This seems like a bug to me. I sent a bug report from the UI (email address is same as on my forum account).