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
In some situation, Updatecli can close and reopen GitHub pullrequest.
In Updatecli version 0.75.0, Updatecli introduced the ability to converge working branch which "diverged" from their base branch.
This has the consequence that a pullrequest may not necessary be needed anymore so now Updatecli can now close pull request that contain no changes.
This new behavior combined with an early design decision which is that Updatecli executes one pipeline at a time can lead to the following situation.
Updatecli loads two pipelines, pipeline A and pipeline B, targeting the same working branch.
Pipeline A is executed
It detects that the working branch diverged
It recreate the working branch, push the changes
It detects an opened pullrequest with nothing to change anymore
It closes the pullrequest
Pipeline B is executed
It detect some changes which need to be applied
It push the change and open a pullrequest as the previous one was closed by Pipeline A
If pipeline B is executed first then obviously there is not issue as Updatecli wouldn't close the pull request.
The major consequence of this workflow is the amount of notification send when pull requests are closed and reopened
Expected Behavior
Instead of running "action" per pipeline, I am considering running them once all pipelines have been executed.
Steps To Reproduce
No response
Environment
- OS: linux
- updatecli: 0.75.0
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
In some situation, Updatecli can close and reopen GitHub pullrequest.
In Updatecli version 0.75.0, Updatecli introduced the ability to converge working branch which "diverged" from their base branch.
This has the consequence that a pullrequest may not necessary be needed anymore so now Updatecli can now close pull request that contain no changes.
This new behavior combined with an early design decision which is that Updatecli executes one pipeline at a time can lead to the following situation.
Updatecli loads two pipelines, pipeline A and pipeline B, targeting the same working branch.
If pipeline B is executed first then obviously there is not issue as Updatecli wouldn't close the pull request.
The major consequence of this workflow is the amount of notification send when pull requests are closed and reopened
Expected Behavior
Instead of running "action" per pipeline, I am considering running them once all pipelines have been executed.
Steps To Reproduce
No response
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: