This repository was archived by the owner on Sep 21, 2026. It is now read-only.
Repository navigation
chore(deploy): push image bumps to application-configuration - #3175
Merged
Merged
Conversation
website moved out of appwrite-labs/assets-applications into the consolidated appwrite-labs/application-configuration repository, which is laid out as <project>/<env>/<app> instead of <env>/<app>. PROJECT now names the project and APPLICATION the app, matching the dns workflows already deploying there; the commit subject keeps naming the app. The values were moved byte-identical and ArgoCD is repointed in cluster-configuration-generator, so this only changes where the bump is written.
Appwrite WebsiteProject ID: Website (appwrite/website)Project ID: Tip Roll back Sites deployments instantly by switching between versions |
Contributor
Greptile SummaryThe PR redirects production and staging image-tag bumps from
Confidence Score: 5/5The PR appears safe to merge after the coordinated external repository and ArgoCD changes described in the required merge order. Both workflows consistently use the new repository, static project/application path segments, and application name, with no internally inconsistent or concretely broken changed path identified. Important Files Changed
Reviews (1): Last reviewed commit: "chore(deploy): push image bumps to appli..." | Re-trigger Greptile |
loks0n
approved these changes
Aug 16, 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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.


What
websitemoved out ofassets-applicationsintoapplication-configuration(appwrite-labs/application-configuration#12), which is laid out as<project>/<env>/<app>instead of<env>/<app>.Affected workflows: production,staging.
PROJECTnow names the project andAPPLICATIONthe app, matching thednsworkflows already deploying to that repo. The commit subject still names the app, so the bump commits read the same as before.The declarative-deployment GitHub App is already installed on
application-configuration— it is what thednspipeline authenticates with.Merge order
Last. ArgoCD has to be reading the new repo first, otherwise a bump lands where nothing syncs from. Order: appwrite-labs/reusable-workflows#10 → appwrite-labs/application-configuration#12 → appwrite-labs/cluster-configuration-generator#158 (plus its generated PR into
cluster-configuration) → this.