Michael Weimann opened 4 years ago
|
|||||||
Michael Weimann changed title 4 years ago
|
|||||||
Reproducing PR: https://onedev.io/projects/michael.test/pulls/1/changes
|
|||||||
Pull request changes is currently calculated by comparing source branch against target branch at the time of creating pull request. I agree that it should be more natural to compare against latest of target branch. Need to investigate it further as some other features such as code comments and review statuses are built upon this assumption. |
|||||||
Uff - this is a quite weird behaviour. The only way reviewing changes is by looking at the "merge preview". |
|||||||
Robin Shen batch edited 4 years ago
|
|||||||
Robin Shen changed title 4 years ago
|
|||||||
Robin Shen changed fields 4 years ago
|
|||||||
OneDev changed state to 'Closed' 4 years ago
|
|||||||
👍 |
|||||||
xg427 changed state to 'Open' 4 years ago
|
|||||||
The state "Closed" in code.onedev.io now means the issue is closed but not released yet. Have you observed incorrect behavior of this fix on master branch? |
|||||||
Robin Shen changed state to 'Closed' 4 years ago
|
|||||||
Change state to "Closed" as work on this issue is done. |
|||||||
OneDev changed state to 'Released' 4 years ago
|
|||||||
OneDev referenced from other issue 4 years ago
|
What I did:
Expected: "Master merge" changes are not displayed as changes