Overview - Zitadel/zitadel

zitadel/zitadel

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
docs-helm-improve
a6b453be fix(telemetry): count IDP template data (#11720) # Which Problems Are Solved The total number of configured IDPs seemed of. We were counting only the IDP table for non-templated IDPs. # How the Problems Are Solved Add a count trigger migration for the IDP template table. Entries will be counted under the existing `ResourceCountIdentityProvider` # Additional Changes - none # Additional Context - Reported internally - Implemented in #9979 - Related https://github.com/zitadel/zitadel/issues/9957 Co-authored-by: Livio Spring <livio.a@gmail.com>
19 days ago by Tim Möhlmann
Succeeded
docs-helm-improve
a6b453be Merge a7aeff4ffd96e9144f38ca9ba5faebec9b01482b into 921414fa164138955a8233a4844ddd4c11c7a28e
19 days ago by Florian Fo...
Succeeded
docs-helm-improve
19 days ago
Succeeded
docs-helm-improve
1dc94cdb docs: tweaking titles for better SEO appeal (#11852) Just updating some title and descriptions for better SEO discovery --------- Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
20 days ago by Florian Fo...
Succeeded
docs-helm-improve
1dc94cdb Merge 08dfc209f1329fc9ea29c5abce19a5e285c3f0cc into 279f592d803e884064c54694c1e9da80f8a8c4d9
20 days ago by Florian Fo...
Succeeded
docs-helm-improve
20 days ago
Succeeded
docs-helm-improve
6a209e80 code review
25 days ago by Florian Fo...
Succeeded
docs-helm-improve
6a209e80 Merge 94e5f6137c9b8abf51ee31fda40aa4e4baaebde0 into 4586708c06401922b9eff32b9f828015f5b085a6
25 days ago by Florian Fo...
Succeeded
docs-helm-improve
25 days ago
Succeeded
docs-helm-improve
e3788007 Merge 7e816b0972f8601169d442c16bf911ebdb533089 into 4586708c06401922b9eff32b9f828015f5b085a6
25 days ago by Florian Fo...
Succeeded
docs-helm-improve
e3788007 update docs
25 days ago by Florian Fo...
Succeeded
docs-helm-improve
25 days ago
Succeeded
docs-helm-improve
d19df975 chore: add terminology Markdown catalog for Copilot review (#11764) ## Problem ZITADEL has inconsistent naming across docs, UI, and API ([#5888](https://github.com/zitadel/zitadel/issues/5888)). We want contributors and Copilot code-review agents to flag discouraged terms and suggest canonical replacements automatically. ## Solution Add a **Markdown terminology catalog** that Copilot agents read natively. ### What's added - **`TERMINOLOGY.md`** (repo root) — full ~35-term canonical table from issue #5888 with: - Action legend: `keep` / `replace` / `remove` / `internal` / `proposed` - Scope legend: `UI` / `Docs` / `API` / `Everywhere` - "Search for (discouraged)" and "Replace with / enforce" columns - Governance section (how to add new terms, ownership) - **`.github/instructions/terminology.instructions.md`** — Copilot `applyTo`-scoped instruction that activates on every PR touching docs/i18n/proto files and tells the agent: - Which files map to which scope - Not to flag identifiers/field names in proto files (only comments/descriptions) - To request catalog updates when new terms are introduced ### What's updated - `.github/copilot-instructions.md` — points to `TERMINOLOGY.md` - `apps/docs/AGENTS.md` — updated reference, removed dead `check-terminology` Nx target entry - `.github/pull_request_template.md` — checklist item updated - `.github/workflows/ready_for_review.yml` — checklist item updated ### Why Markdown over JSON | | Markdown | JSON | |---|---|---| | Copilot reads natively | yes | no (needs parsing context) | | Mirrors AGENTS.md table style | yes | no | | Human-readable without tooling | yes | no | | Mirrors the #5888 issue format | yes | no | | Requires schema / parser | no | yes | ### Why root over `.github/` `.github/` is for GitHub-specific automation files. `TERMINOLOGY.md` is a project-wide convention document — it belongs alongside `CONTRIBUTING.md`, `CODE_OF_CONDUCT.md`, and `AGENTS.md` at the repo root. ## How it works in practice When a PR touches `apps/docs/content/**`, `console/src/assets/i18n/**`, `apps/login/locales/**`, or `proto/**/*.proto`, Copilot code review automatically loads `.github/instructions/terminology.instructions.md` and cross-references `TERMINOLOGY.md` to flag discouraged terms. Human reviewers see the terminology checklist in the auto-comment on PR open. ## Checklist - [x] `TERMINOLOGY.md` at repo root with all ~35 terms from #5888 - [x] Plain text action/scope values (no emojis) - [x] Copilot instruction file scoped to correct file patterns - [x] All stale `terminology-rules.json` references removed - [x] No linter/CI step added (guidelines-only approach) Relates to: #5888 --------- Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Co-authored-by: Fabienne Bühler <fabienne@zitadel.com>
25 days ago by Florian Fo...
Succeeded
docs-helm-improve
d19df975 Merge dbb5221fda832799ea6ba7d6bef008ac55b9223d into 4586708c06401922b9eff32b9f828015f5b085a6
25 days ago by Florian Fo...
Succeeded
docs-helm-improve
25 days ago
Succeeded
docs-helm-improve
47d4d070 feat: delete metadata on SetUserMetadata api (#11776) # Which Problems Are Solved Currently, to delete metadata a key, callers must use a separate [DeleteMetadata](https://zitadel.com/docs/reference/api/user/zitadel.user.v2.UserService.DeleteUserMetadata) API. This increases the complexity on client-side for operations where metadata need to be synchronized. # How the Problems Are Solved Introduce the behavior to [SetUserMetadata](https://zitadel.com/docs/reference/api/user/zitadel.user.v2.UserService.SetUserMetadata): When a metadata entry is passed with an empty value ("" / empty bytes): - If the key exists → delete the key - If the key does not exist → no-op (idempotent, no error) # Additional Changes - Updated [User Metadata page](https://zitadel.com/docs/guides/manage/customize/user-metadata#manage-user-metadata-through-the-management-api) # Additional Context Similar behavior will be applied to [UpdateUser](https://zitadel.com/docs/reference/api/user/zitadel.user.v2.UserService.UpdateUser) and [SetOrganizationMetadata](https://zitadel.com/docs/reference/api/org/zitadel.org.v2.OrganizationService.SetOrganizationMetadata) Breaking change? Currently, sending an empty value returns an error — no client should be intentionally relying on that error as part of a working workflow. The change goes from "rejected input" to "accepted input with defined semantics." In other words, it relaxes a restriction rather than tightening one. Existing valid calls continue to work exactly as before. The only scenario where it could be "breaking" is if someone explicitly depends on the error response for empty values (e.g., using it as a validation check), which would be unusual. --------- Co-authored-by: Gayathri Vijayan <gayathri+github@zitadel.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 month ago by Vitor Bari...
Succeeded
docs-helm-improve
47d4d070 Merge 90ebcb8c941d15670e493f67614631ea24cbd90c into 247e2785052957c86c3e0b16148617d26d6be511
1 month ago by Florian Fo...
Succeeded
docs-helm-improve
1 month ago
Succeeded
docs-helm-improve
6ec059af docs: update quickstart URL to port 8080 matching Docker Compose Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 month ago by Florian Fo...
Succeeded
docs-helm-improve
6ec059af Merge 53da2dbb9ca4dfa6a7ac21fbd37ebb3f146ec840 into 07dbb48cc788c323743ed9f62eb64991355c01ce
1 month ago by Florian Fo...