Tell agents to use --autoapprove when a config apply only creates infrastructure - #59
Merged
Merged
Conversation
…frastructure Co-Authored-By: brandon <brandon@flightcontrol.dev>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
flybayer
approved these changes
Aug 19, 2026
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
Agents following the project config workflow applied without
--autoapprove, so every stack run for brand-new infrastructure stalled at a manual approval gate — an unnecessary human round trip when nothing existing is being modified or destroyed.The agent-facing guidance (
start-here.mdxagent workflow,project-config-file.mdx"Apply the changes" step and Agent tips) now says: pass--autoapprovewhen the apply only creates new environments/module instances, and omit it when the change modifies, replaces, or removes existing infrastructure so a human reviews the Terraform plan.Link to Devin session: https://app.devin.ai/sessions/a33d999f0ee54a79b8c57d6ca1b83287
Requested by: @flybayer
Greptile Summary
The PR updates agent-facing project-config guidance to use
--autoapprovefor changes that only create infrastructure while retaining manual Terraform-plan approval for changes affecting existing resources.Confidence Score: 5/5
The documentation-only change appears safe to merge, with no concrete actionable defects identified.
The updated guidance consistently limits automatic approval to create-only applies and retains manual review for modifications, replacements, and removals of existing infrastructure.
Important Files Changed
--autoapproveand preserves the separate manual and automatic stack-run follow-up flows.Reviews (1): Last reviewed commit: "Tell agents to pass --autoapprove when a..." | Re-trigger Greptile