- 
                Notifications
    
You must be signed in to change notification settings  - Fork 279
 
blog: fix non-interactive client command flags and placeholders in CI/CD article #2564
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…/CD examples article
          
WalkthroughA documentation file containing CI/CD examples for Appwrite was updated to reflect a new appwrite client command syntax. The command parameters were modified across multiple example blocks, including changes to flag names (projectId to project-id), parameter reordering (endpoint moved first), addition of quotes around values, and updated placeholder syntax. No functional code changes or API modifications were made. Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 
 Pre-merge checks and finishing touches✅ Passed checks (2 passed)
 ✨ Finishing touches🧪 Generate unit tests (beta)
 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. Comment   | 
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
src/routes/blog/post/ci-cd-examples-in-appwrite/+page.markdoc (1)
70-99: Consider standardizing placeholder format for consistency.The document uses different placeholder styles:
function_id(line 70),collection_id(line 77),<YOUR-PROJECT-ID>(line 85), andMFA_CODE(line 99). While this doesn't affect functionality, standardizing to a single format (e.g., consistently using<YOUR-...>orALL_CAPS) would improve readability.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
src/routes/blog/post/ci-cd-examples-in-appwrite/+page.markdoc(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: stnguyen90
Repo: appwrite/website PR: 2520
File: src/routes/docs/advanced/self-hosting/production/updates/+page.markdoc:13-15
Timestamp: 2025-10-24T22:17:14.669Z
Learning: In Appwrite versioning, RC (Release Candidate) versions like `1.6.2-RC1` come before the stable release `1.6.2`. Documentation should recommend upgrading to stable versions, not RC versions.
📚 Learning: 2025-09-25T05:26:19.287Z
Learnt from: BretRen
Repo: appwrite/website PR: 2442
File: src/routes/docs/products/auth/email-password/+page.markdoc:22-31
Timestamp: 2025-09-25T05:26:19.287Z
Learning: Appwrite JavaScript SDKs now support object-based arguments instead of positional arguments as of 2025. The account.create method should be called with an object parameter containing userId, email, password, and optional name, rather than positional arguments. Positional arguments still work but are deprecated.
Applied to files:
src/routes/blog/post/ci-cd-examples-in-appwrite/+page.markdoc
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: build
 - GitHub Check: tests
 
🔇 Additional comments (1)
src/routes/blog/post/ci-cd-examples-in-appwrite/+page.markdoc (1)
85-85: LGTM! Command syntax fix is correct.The update to kebab-case flags (
--project-idinstead of--projectId) is consistent with CLI standards and matches the flag format used elsewhere in the document. The addition of quotes around values and the more explicit endpoint URL format (https://<YOUR-ENDPOINT>/v1) are good improvements for clarity.
What does this PR do?
Fixes non-interactive client command flags
Summary by CodeRabbit