build: added more clarification for loading scripts
CI / benchmark-regression (push) Failing after 0s
CI / benchmark-publish (push) Failing after 0s
CI / lint (push) Successful in 22s
CI / quality (push) Successful in 22s
CI / typecheck (push) Successful in 45s
CI / security (push) Successful in 46s
CI / build (push) Successful in 26s
CI / helm (push) Successful in 32s
CI / push-validation (push) Successful in 22s
CI / e2e_tests (push) Successful in 3m58s
CI / unit_tests (push) Successful in 7m45s
CI / integration_tests (push) Successful in 7m42s
CI / docker (push) Successful in 56s
CI / coverage (push) Successful in 9m48s
CI / status-check (push) Successful in 1s
CI / benchmark-regression (push) Failing after 0s
CI / benchmark-publish (push) Failing after 0s
CI / lint (push) Successful in 22s
CI / quality (push) Successful in 22s
CI / typecheck (push) Successful in 45s
CI / security (push) Successful in 46s
CI / build (push) Successful in 26s
CI / helm (push) Successful in 32s
CI / push-validation (push) Successful in 22s
CI / e2e_tests (push) Successful in 3m58s
CI / unit_tests (push) Successful in 7m45s
CI / integration_tests (push) Successful in 7m42s
CI / docker (push) Successful in 56s
CI / coverage (push) Successful in 9m48s
CI / status-check (push) Successful in 1s
This commit is contained in:
@@ -80,11 +80,11 @@ Before starting the main loop below be sure to create your status tracking ticke
|
||||
|
||||
In an infinite loop do the following each cycle:
|
||||
1. If at least 10 minutes has passed since the last time you updated your automation tracking status ticket, or if you never created/updated one, (see tracking section below) then update your tracking ticket using the `automation-tracking-manager` subagent according to the details provided in the section labeled "tracking" below.
|
||||
2. Use the script `list_prs_ready_to_merge` from the `auto-agents-system` skill, if the list is empty skip to the next step, however, if it has one or more PR in it then sequentially dispatch a single `pr-merge-worker` subagent for each PR in the group and then start the cycle over at #1 (skipping the rest of the steps in this cycle)
|
||||
3. Use the script `list_prs_stale_clean` from the `auto-agents-system` skill, if the list is empty skip to the next step, however, if it has one or more PR in it then sequentially dispatch a single `pr-merge-worker` subagent for each PR in the group and then start the cycle over at #1 (skipping the rest of the steps in this cycle)
|
||||
4. Use the script `list_prs_stale_conflicts` from the `auto-agents-system` skill, if the list is empty skip to the next step, however, if it has one or more PR in it then sequentially dispatch a single `pr-merge-worker` subagent for each PR in the group and then start the cycle over at #1 (skipping the rest of the steps in this cycle)
|
||||
5. Use the script `list_prs_needs_review_stale_clean` from the `auto-agents-system` skill, if the list is empty skip to the next step, however, if it has one or more PR in it then sequentially dispatch a single `pr-merge-worker` subagent for each PR in the group and then start the cycle over at #1 (skipping the rest of the steps in this cycle)
|
||||
6. Use the script `list_prs_needs_review_stale_conflicts` from the `auto-agents-system` skill, if the list is empty skip to the next step, however, if it has one or more PR in it then sequentially dispatch a single `pr-merge-worker` subagent for each PR in the group and then start the cycle over at #1 (skipping the rest of the steps in this cycle)
|
||||
2. Use the script `list_prs_ready_to_merge` from the `auto-agents-system` skill which you must load and query how to use the mentioned skill, if the list is empty skip to the next step, however, if it has one or more PR in it then sequentially dispatch a single `pr-merge-worker` subagent for each PR in the group and then start the cycle over at #1 (skipping the rest of the steps in this cycle)
|
||||
3. Use the script `list_prs_stale_clean` from the `auto-agents-system` skill which you must load and query how to use the mentioned skill, if the list is empty skip to the next step, however, if it has one or more PR in it then sequentially dispatch a single `pr-merge-worker` subagent for each PR in the group and then start the cycle over at #1 (skipping the rest of the steps in this cycle)
|
||||
4. Use the script `list_prs_stale_conflicts` from the `auto-agents-system` skill which you must load and query how to use the mentioned skill, if the list is empty skip to the next step, however, if it has one or more PR in it then sequentially dispatch a single `pr-merge-worker` subagent for each PR in the group and then start the cycle over at #1 (skipping the rest of the steps in this cycle)
|
||||
5. Use the script `list_prs_needs_review_stale_clean` from the `auto-agents-system` skill which you must load and query how to use the mentioned skill, if the list is empty skip to the next step, however, if it has one or more PR in it then sequentially dispatch a single `pr-merge-worker` subagent for each PR in the group and then start the cycle over at #1 (skipping the rest of the steps in this cycle)
|
||||
6. Use the script `list_prs_needs_review_stale_conflicts` from the `auto-agents-system` skill which you must load and query how to use the mentioned skill, if the list is empty skip to the next step, however, if it has one or more PR in it then sequentially dispatch a single `pr-merge-worker` subagent for each PR in the group and then start the cycle over at #1 (skipping the rest of the steps in this cycle)
|
||||
7. Sleep for 5 minutes using `bash("sleep 300", timeout=360000)`.
|
||||
8. Loop through the cycle indefinately by starting at step 1 above again.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user