feat(cmd): add hidden flag aliases for devcontainer CLI compat

[skevetter]

Summary

Adds hidden cobra flag aliases on the up command to match the official devcontainer CLI naming conventions, improving compatibility for users migrating from or scripting against the standard CLI.

Aliases added:

• --override-config → alias for --extra-devcontainer-path (matches devcontainer up --override-config)
• --dotfiles-repository → alias for --dotfiles (matches devcontainer up --dotfiles-repository)
• --remove-existing-container → alias for --recreate (matches devcontainer up --remove-existing-container)

Aliases skipped (with reasons):

• --workspace-folder on up: Currently a positional arg (up [workspace-path]). Adding as a flag would conflict with positional arg semantics. The exec command already uses --workspace-folder as an explicit flag.
• --remote-env on up: The official CLI only has --remote-env on exec (not up). Our --workspace-env on up has different semantics (injected during workspace creation, not remote container env).
• --container-data-folder / --container-system-data-folder: No equivalent flags exist in our CLI.
• --mount: Not an official devcontainer CLI flag. The official CLI has --mount-workspace-git-root instead, which is semantically different from our --workspace-mount-consistency.
• --id-label: Already uses the same name as the official CLI — no alias needed.

All aliases are hidden (don't appear in --help) and bind to the same variable as the primary flag. Unit tests cover both value binding and hidden status for each alias.

[netlify]

✅ Deploy Preview for devsydev canceled.

Name	Link
🔨 Latest commit	31f2535
🔍 Latest deploy log	https://app.netlify.com/projects/devsydev/deploys/69f8538105c1f50008c0bdc6

[coderabbitai]

Warning

Rate limit exceeded

@skevetter has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 46 minutes and 41 seconds before requesting another review.

To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 1943fd23-8051-4667-b022-c1f1ec14c636

📥 Commits

Reviewing files that changed from the base of the PR and between e2992f8 and 31f2535.

📒 Files selected for processing (2)

• cmd/flag_aliases_test.go
• cmd/up.go

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 46 minutes and 41 seconds.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}