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
Whenever niv-updater-action needs to create a new branch, it triggers two different push events, one for the branch creation, another for the commit containing the actual niv dependencies update.
We are using github actions on our repositories. Having two events means github actions are triggered once for the branch (copy of the base branch) and a second time for the commit. We tried to use concurency to cancel the first run but it randomly cancel the right one.
Would it be an option to use the git client to push the created the branch and the commit at once ?
The text was updated successfully, but these errors were encountered:
Hi @jfroche thanks for reporting this issue. I think I initially implemented it this way to that one doesn't have to have a checkout of the code. I'll try to implement it over the weekend by either using the API to achieve the same, or have an option to use git executable (if one already has checked out the code).
Whenever niv-updater-action needs to create a new branch, it triggers two different push events, one for the branch creation, another for the commit containing the actual niv dependencies update.
We are using github actions on our repositories. Having two events means github actions are triggered once for the branch (copy of the base branch) and a second time for the commit. We tried to use concurency to cancel the first run but it randomly cancel the right one.
Would it be an option to use the git client to push the created the branch and the commit at once ?
The text was updated successfully, but these errors were encountered: