docs: clarify deployment block nesting in llms.txt#17
Merged
vigneshrajsb merged 1 commit intomainfrom Feb 12, 2026
Merged
Conversation
Add explicit guidance for where deployment blocks should be nested: - For github services: inside github at same level as docker - For docker services: inside docker block Also added complete examples showing correct structure for both service types, including nginx example with deployment. Co-authored-by: Cursor <cursoragent@cursor.com>
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
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.
Summary
deploymentblocks should be nested for both service typesdeploymentgoes insidegithub:at the same level asdocker:deploymentgoes insidedocker:deploymentto Docker service template and Redis exampleContext
When agents use the llms.txt to generate lifecycle.yaml configs, they were placing the
deploymentblock at the wrong level (at service level instead of inside the service type block). These changes make the correct nesting structure explicit.Test plan
Made with Cursor