Document that project config apply can create the project

[devin-ai-integration]

Summary

ravion project config apply <project-id> now creates the project when it does not exist yet and the config file's project.givenId matches <project-id> (--dry-run plans that creation without writing), so ravion project create is no longer a required first step when you already have a config file. Adds that note to the pull-and-apply steps and the deploy-an-app assistant skill, and regenerates the project config apply help text on the CLI reference page.

Depends on https://github.com/ravionhq/flightcontrol/pull/7045 — merge after that ships.

ENG-5202

Link to Devin session: https://app.devin.ai/sessions/5f8b39c935554413a00acb3020a9254e
Requested by: @flybayer

Greptile Summary

The PR documents that ravion project config apply can create a missing project when its given ID matches the config, including dry-run behavior.

• Updates the generated project CLI reference with creation semantics.
• Adds the creation-via-apply path to the project config guide.
• Teaches the deployment assistant skill about skipping explicit project creation when a config already exists.

Confidence Score: 4/5

The PR appears safe to merge, with a non-blocking clarification needed in the deployment assistant’s alternative command flow.

The reference and config guide describe the new behavior consistently, but the assistant skill still directs the skip-create path through an unconditional pull from the not-yet-created project.

Files Needing Attention: .mintlify/assistant/skills/deploy-an-app/skill.md

Important Files Changed

Filename	Overview
.mintlify/assistant/skills/deploy-an-app/skill.md	Adds the creation-via-apply guidance, but leaves project config pull unconditional in the alternative workflow.
cli/reference/project.mdx	Regenerates the apply command description with missing-project creation and dry-run semantics.
config-as-code/project-config-file.mdx	Adds a note explaining when users with an existing config can skip explicit project creation.

Prompt To Fix All With AI

### Issue 1
.mintlify/assistant/skills/deploy-an-app/skill.md:68-69
**Skip the pull command too**

For a new project with an existing config file, this comment says to skip only `project create`, leaving the linear workflow to pull configuration from a project that does not exist before reaching the apply command that creates it. Explicitly skip both preceding commands for this path so the generated instructions are internally consistent.

```suggestion
# Already have a config file? Skip `project create` and `project config pull`: apply creates the
# project when it does not exist yet and the file's project.givenId matches the given ID passed here.
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "Document that project config apply can c..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
Ravion	🟢 Ready	View Preview	Aug 19, 2026, 11:05 PM

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[greptile-apps]

Skip the pull command too

For a new project with an existing config file, this comment says to skip only project create, leaving the linear workflow to pull configuration from a project that does not exist before reaching the apply command that creates it. Explicitly skip both preceding commands for this path so the generated instructions are internally consistent.

Suggested change

	# Already have a config file? Skip `project create`: apply creates the project when it does not
	# exist yet and the file's project.givenId matches the given ID you pass here.
	# Already have a config file? Skip `project create` and `project config pull`: apply creates the
	# project when it does not exist yet and the file's project.givenId matches the given ID passed here.

Prompt To Fix With AI

This is a comment left during a code review.
Path: .mintlify/assistant/skills/deploy-an-app/skill.md
Line: 68-69

Comment:
**Skip the pull command too**

For a new project with an existing config file, this comment says to skip only `project create`, leaving the linear workflow to pull configuration from a project that does not exist before reaching the apply command that creates it. Explicitly skip both preceding commands for this path so the generated instructions are internally consistent.

```suggestion
# Already have a config file? Skip `project create` and `project config pull`: apply creates the
# project when it does not exist yet and the file's project.givenId matches the given ID passed here.
```

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[devin-ai-integration]

Good catch — config pull against a nonexistent project can't work either. Applied your suggestion in 3cff067.