docs(#1636): clarify workflow_call nesting limits and thin-caller guidance - #1643
Closed
fullsend-ai-coder[bot] wants to merge 1 commit into
Closed
docs(#1636): clarify workflow_call nesting limits and thin-caller guidance#1643fullsend-ai-coder[bot] wants to merge 1 commit into
fullsend-ai-coder[bot] wants to merge 1 commit into
Conversation
…dance Update the stale 4-level workflow_call nesting limit to the current 10-level limit (50 calls per run, raised by GitHub in November 2025) in ADR 0041 and ADR 0031. Add nesting arithmetic to ADR 0041 Consequences documenting the full synchronous chain (shim → dispatch → thin caller → reusable = 3 of 10 levels) and explaining why thin callers remain valuable despite consuming a nesting level: explicit secrets passthrough and vars to inputs mapping that makes the reusable workflow parameter contract visible and auditable. Add a living-docs bullet to docs/architecture.md covering event-driven stage dispatch, nesting arithmetic, and thin-caller rationale. Note: make lint could not run — pre-commit gitleaks hook fails to install in sandbox due to Go toolchain permission error. Changes are documentation-only (3 Markdown files); no Go code affected. Closes #1636
Site previewPreview: https://abe0619b-site.fullsend-ai.workers.dev Commit: |
ReviewFindingsNo findings. |
![fullsend-ai-review[bot]](https://avatars.githubusercontent.com/in/3478501?s=60&v=4){kind=small}
fullsend-ai-review
Bot
added
the
ready-for-merge
Member
|
Closing as this is already fixed in #1578 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Update the stale 4-level workflow_call nesting limit to the current 10-level limit (50 calls per run, raised by GitHub in November 2025) in ADR 0041 and ADR 0031.
Add nesting arithmetic to ADR 0041 Consequences documenting the full synchronous chain (shim → dispatch → thin caller → reusable = 3 of 10 levels) and explaining why thin callers remain valuable despite consuming a nesting level: explicit secrets passthrough and vars to inputs mapping that makes the reusable workflow parameter contract visible and auditable.
Add a living-docs bullet to docs/architecture.md covering event-driven stage dispatch, nesting arithmetic, and thin-caller rationale.
Note: make lint could not run — pre-commit gitleaks hook fails to install in sandbox due to Go toolchain permission error. Changes are documentation-only (3 Markdown files); no Go code affected.
Closes #1636
Post-script verification
agent/1636-clarify-nesting-limits)8480e16153a3f16c66b5484bfd4c76349a89933d..HEAD)