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
Copy file name to clipboardExpand all lines: README.md
-9Lines changed: 0 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,15 +15,6 @@ In repositories with a lot of activity, the workflow queue will get backed up ve
15
15
16
16
Dispatching commands to be processed elsewhere keeps the workflow queue moving quickly. It essentially enables parallel processing of workflows.
17
17
18
-
### Key features
19
-
20
-
- Enables separating the queue of `issue_comment` events from the queue of dispatched commands to keep it fast moving
21
-
- Users receive faster feedback that commands have been seen and are waiting to be processed
22
-
- The ability to handle processing commands in multiple repositories in parallel
23
-
- Long running workloads can be separated to a repository workflow queue of their own
24
-
25
-
Even if commands are dispatched and processed in the same repository, separation of comment parsing and command processing makes workflows more maintainable, and with less duplication.
26
-
27
18
### Demo and examples
28
19
29
20
The best way to understand how this works is to try it out for yourself.
0 commit comments