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
There is a wierd behavior which looks like some kind of 'glitch' on github but as its not the first time wanted to raise it here.
there seems to be an issue with the exact same issue which was closed (#1431)
we have a flow of automatic release-deploy which being triggered while merging PR to master.
basically we have the following 2 workflows :
when PR merged to master --> Release flow executed and create a new release
when release created --> new Deploy flow executed and deploy the latest tag
it works like that for many microservices, but suddenly after release created and the deploy job triggered, the checkout phase checked out the latest commit on master instead the latest tag created.
the Event for the deploy job is:
on:
release:
types: [created]
and the checkout looks like that:
- uses: actions/checkout@v3
with:
fetch-depth: 0
is it just a 'glitch'?
anything we can do about it?
10x
The text was updated successfully, but these errors were encountered:
Hi
There is a wierd behavior which looks like some kind of 'glitch' on github but as its not the first time wanted to raise it here.
there seems to be an issue with the exact same issue which was closed (#1431)
we have a flow of automatic release-deploy which being triggered while merging PR to master.
basically we have the following 2 workflows :
it works like that for many microservices, but suddenly after release created and the deploy job triggered, the checkout phase checked out the latest commit on master instead the latest tag created.
the Event for the deploy job is:
and the checkout looks like that:
is it just a 'glitch'?
anything we can do about it?
10x
The text was updated successfully, but these errors were encountered: