What is CI/CD? A complete guide for developers#3062
Conversation
Appwrite WebsiteProject ID: Website (appwrite/website)Project ID: Tip Silent mode disables those chatty PR comments if you prefer peace and quiet |
Greptile SummaryThis PR adds a new SEO blog post titled "What is CI/CD? A complete guide for developers", along with its cover image and a corresponding
Confidence Score: 5/5Safe to merge once the previously raised author attribution is resolved — the blog content, image, and cache entry are all in order. The change is a new blog post and its associated assets. Content is well-structured, FAQs are accurate, and the Appwrite resource links at the bottom are relevant to the topic. No logic, data, or application behavior is affected. No files require special attention beyond confirming the author field is corrected before publishing (flagged in a prior review thread). Important Files Changed
Reviews (5): Last reviewed commit: "Update +page.markdoc" | Re-trigger Greptile |
| date: 2026-06-26 | ||
| cover: /images/blog/what-is-cicd-a-complete-guide-for-developers/cover.avif | ||
| timeToRead: 5 | ||
| author: atharva |
There was a problem hiding this comment.
The
author field is set to atharva, but this PR is submitted by aishwaripahwa12, whose GitHub handle is registered to the aishwari author slug (Aishwari Pahwa). Every other post submitted from this GitHub account uses author: aishwari. Using atharva will credit Atharva Deosthale for a post he did not write.
| author: atharva | |
| author: aishwari |
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!
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
|
|
||
| Each stage acts as a gate: if a step fails, the pipeline stops and the team is notified, so broken code never reaches users. Many pipelines also include extra stages for security scanning, performance checks, and approvals. | ||
|
|
||
| # Continuous delivery vs continuous deployment: What's the difference? |
There was a problem hiding this comment.
This section feels redundant, we already discussed above.
|
|
||
| Appwrite is open-source, self-hostable, and built for developers who want to ship fast without surrendering control. Recent releases have added [MongoDB support, Appwrite 1.9.0, realtime upgrades, and new AI tooling](https://dev.to/appwrite/april-product-update-mongodb-support-appwrite-190-realtime-upgrades-and-ai-tooling-1eg6), with [more landing every few weeks](https://dev.to/appwrite/may-product-update-presences-api-rust-runtime-7x-faster-storage-uploads-and-more-9h5). We post weekly roundups of product announcements, AI updates, and [developer insights](https://dev.to/appwrite/weekly-roundup-presences-api-git-deployment-triggers-and-ai-updates-58lj) on the [Appwrite blog](https://appwrite.io/blog) and across our developer channels, so follow along wherever you read. | ||
|
|
||
| Whether you are prototyping your next idea or scaling a production app, Appwrite gives you auth, databases, storage, functions, and real-time in one place, all open-source. [Sign up for Appwrite Cloud](https://cloud.appwrite.io/) or spin up a self-hosted instance in minutes, and give your next build a real backend to grow on. |
There was a problem hiding this comment.
We should also mention Sites.
Co-authored-by: Atharva Deosthale <atharva.deosthale17@gmail.com>


Latest SEO blog