3 ms·
sure, in order to deploy at my company you have to tag it and then wait. You can't do the next tag until that first tag's action is done. So I end up refreshing
by andrewfromx 2y ago
sure, in order to deploy at my company you have to tag it and then wait. You can't do the next tag until that first tag's action is done. So I end up refreshing the github actions page over and over. Or I go do something else and then forget about it and now the deploy is delayed. And it's not just 1 more tag. It's a series of tags before the thing is finally deployed and live. This give me just 1 thing to run and then I can walk away and know that each step has been done as soon as possible with me the human not having to do anything more.
- JTyQZSnP3cQGa8B 2y agoIt looks like a pipeline or process problem that should be solved elsewhere. What happens if I make 10 tags at once? And why would I be allowed to do that? Do you have that authority or are those random tags that are destroyed later?