You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I have a use case for the "on synchronize" event, which I will illustrate as follows:
I created a pull request with the base branch as "develop" and the current branch as "feature/xyz".
Let's assume the current SHA of the "feature/xyz" branch is SHA 111.
I made changes to "file1.txt" and pushed the changes with a commit SHA of SHA 222.
I was able to detect the change correctly on the "feature/xyz" branch (from SHA 111 to SHA 222).
However, I am facing a challenge now.
Let's assume that I made another change to "file2.txt" on my local machine. I committed my changes but didn't push them (SHA 333).
Then, I made a change to "file3.txt" on my local machine, committed my changes and pushed them (SHA 444).
But when the triggered build checked in, I can only see that the changed file is "file3.txt" because the comparison is between SHA 444 and SHA 333. What I actually need is a comparison between SHA 444 and SHA 222, as SHA 333 was a local commit and came with the SHA 444 push.
Describe the solution you'd like?
In summary, I want to compare the last remote SHA of the current branch (SHA 222) with the head SHA of the current branch (SHA 444)
It is even possible?
Describe alternatives you've considered?
No response
Anything else?
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
Is this feature missing in the latest version?
Is your feature request related to a problem? Please describe.
I have a use case for the "on synchronize" event, which I will illustrate as follows:
I created a pull request with the base branch as "develop" and the current branch as "feature/xyz".
Let's assume the current SHA of the "feature/xyz" branch is SHA 111.
I made changes to "file1.txt" and pushed the changes with a commit SHA of SHA 222.
I was able to detect the change correctly on the "feature/xyz" branch (from SHA 111 to SHA 222).
However, I am facing a challenge now.
Let's assume that I made another change to "file2.txt" on my local machine. I committed my changes but didn't push them (SHA 333).
Then, I made a change to "file3.txt" on my local machine, committed my changes and pushed them (SHA 444).
But when the triggered build checked in, I can only see that the changed file is "file3.txt" because the comparison is between SHA 444 and SHA 333. What I actually need is a comparison between SHA 444 and SHA 222, as SHA 333 was a local commit and came with the SHA 444 push.
Describe the solution you'd like?
In summary, I want to compare the last remote SHA of the current branch (SHA 222) with the head SHA of the current branch (SHA 444)
It is even possible?
Describe alternatives you've considered?
No response
Anything else?
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: