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 think we should process events from one repository (or maybe from one issue) in a sequential order. For example if the maintainer adds labels and closes the issue, the second event might be executed before the first one because of the async nature of Github Actions which could cause potential bugs.
But there might be scenarios where sequential execution is unwanted for example there is a long running task triggered by a command - in this situation we still want to execute other events while the task is running.
The text was updated successfully, but these errors were encountered:
Can you organize your research and any context you have and include it here? It will provide sufficient context so that somebody else, like @FernandVEYRIER can jump in and help if you want it to be worked on concurrently to your other work.
I think we should process events from one repository (or maybe from one issue) in a sequential order. For example if the maintainer adds labels and closes the issue, the second event might be executed before the first one because of the async nature of Github Actions which could cause potential bugs.
But there might be scenarios where sequential execution is unwanted for example there is a long running task triggered by a command - in this situation we still want to execute other events while the task is running.
The text was updated successfully, but these errors were encountered: