Closed stefango closed 2 years ago
Hi @stefango digging deeper into this. My thoughts on scenario and some questions:
This looks like there might be smth wrong with refreshing inline blame. I'll review the code but that mechanism is triggered when commit hash changes when switching branches / pulling
@zielu Thx for response. My reply is as below:
Git tool window
means the git log tab in Webstorm? If so, the commit hash on develop is HASH_C.I also think there might be smth wrong with refreshing inline blame.
@stefango could you check one more thing ? Does invoking action under Git > GitToolBox > Refresh Blame
fix things ? You could also try moving caret to different line and back.
I see two reasons why old data might be shown:
@zielu Sorry for the late response. I think update develop (the target branch) branch before switching branches is a must. I don't reproduce this issue any more by doing this. Thx.
Ok, I get it now - there was no update done. Plugin does not do any such modifications by design, only thing it does is fetching which is safe as it does not modify the workspace in any way.
Hi. I create my MR with
squash commit
option checked on Gitlab. Commit A (the first commit in this MR) and B are combined into commit A. When I switch into develop branch, commit B will still show inline until restart my Webstorm. I am wondering that is it just designed like this.