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
I have two workflows. Both trigger github-pages-deploy-action. Each workflow updates a directory on the gh-page branch:
workflowA --> deploy --> change content in directoryA
workflowB --> deploy --> change content in directoryB
The problem that I have is if workflowA finishes and starts deploying content to directoryA and workflowB finishes and starts deploying to directoryB then the first deploy gets cancelled and I loose all the data that is in directoryA. How can I force that the first deployment does not get cancelled. I am aware of the concurrency parameter but I don't think it helps me because workflowA and workflowB are allowed to run concurrently.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have two workflows. Both trigger github-pages-deploy-action. Each workflow updates a directory on the gh-page branch:
The problem that I have is if
workflowA
finishes and starts deploying content todirectoryA
andworkflowB
finishes and starts deploying todirectoryB
then the first deploy gets cancelled and I loose all the data that is indirectoryA
. How can I force that the first deployment does not get cancelled. I am aware of the concurrency parameter but I don't think it helps me because workflowA and workflowB are allowed to run concurrently.Any ideas?
Beta Was this translation helpful? Give feedback.
All reactions