zitadel
Team
zitadel/zitadel
Sign in / Sign up
Open main menu
zitadel/zitadel
GitHub
Overview
Runs
Analytics
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
Succeeded
fix-setup-log
a9e17f44 sync other defaults
8 days ago
by muhlemmer
m
Succeeded
fix-setup-log
a9e17f44 Merge 365a634200040330f78dc54665b3ccd283d91a27 into c02d812b6c7d483834d5e263d31d4a24a0076447
8 days ago
by muhlemmer
m
Succeeded
fix-group-mask
3b885698 docs(slog): clarify masking behavior for group vs non-group attributes (#11612) # Which Problems Are Solved Documentation in `cmd/defaults.yaml` and `cmd/mirror/defaults.yaml` incompletely described attribute masking behavior after recent changes to support group masking. The docs explained group attribute masking but omitted the distinct behavior for non-group attributes with nested values. # How the Problems Are Solved Extended documentation comments in both configuration files to describe both masking behaviors: - **Group attributes** (`slog.Group`): Individual values masked, structure preserved - **Non-group attributes** (`slog.Any` with nested objects/arrays): Entire value replaced, structure not preserved This matches the documentation already present in `cmd/setup/steps.yaml`. # Additional Changes None. # Additional Context - Addresses review feedback on PR #11606 - Ensures consistency across all three runtime configuration files <!-- START COPILOT CODING AGENT TIPS --> --- ✨ Let Copilot coding agent [set things up for you](https://github.com/zitadel/zitadel/issues/new?title=✨+Set+up+Copilot+instructions&body=Configure%20instructions%20for%20this%20repository%20as%20documented%20in%20%5BBest%20practices%20for%20Copilot%20coding%20agent%20in%20your%20repository%5D%28https://gh.io/copilot-coding-agent-tips%29%2E%0A%0A%3COnboard%20this%20repo%3E&assignees=copilot) — coding agent works faster and does higher quality work when set up for your repo. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: muhlemmer <5411563+muhlemmer@users.noreply.github.com>
8 days ago
by muhlemmer
m
Succeeded
fix-group-mask
3b885698 Merge 3d76916fb8dbf92ae5460945f4a7a001615d66bc into 93a4ed8857a63b24db56d17626827c662beb7579
8 days ago
by muhlemmer
m
Succeeded
fix-group-mask
403ae72d Merge afe0e85632f746298eb413bf1f8f54915746903d into 93a4ed8857a63b24db56d17626827c662beb7579
8 days ago
by muhlemmer
m
Succeeded
fix-group-mask
cba2a9b4 Update backend/v3/instrumentation/slog.go Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
8 days ago
by muhlemmer
m
Succeeded
fix-group-mask
cba2a9b4 Merge 7ffbe1099fd573cf4751bbd2a08624342b3ba73e into 93a4ed8857a63b24db56d17626827c662beb7579
8 days ago
by muhlemmer
m
Succeeded
fix-group-mask
354b8635 update defaults comments
9 days ago
by muhlemmer
m
Succeeded
fix-group-mask
354b8635 Merge 1d7dda84e4c39da1360a6c69832ea646312d0db7 into db9ebbbb41f3267cd92e95b01efac2901cb9b297
9 days ago
by muhlemmer
m
Succeeded
fix-group-mask
1b4c5a0e fix(slog): masking of grouped attributes
9 days ago
by muhlemmer
m
Succeeded
fix-group-mask
1b4c5a0e Merge 796f47a6b682c04a5ca9a89119aa4fc5b2461405 into db9ebbbb41f3267cd92e95b01efac2901cb9b297
9 days ago
by muhlemmer
m
Succeeded
main
96130b72 fix(benchmark): set proper audience to introspect token (#11586) # Which Problems Are Solved Benchmark appears to run correctly, however the token used isn't valid. The backend (Zitadel 4.11-pre) prints a constant stream of info logs that the token isn't valid for the client. # How the Problems Are Solved Pass the generated project IDs as a scope for a new login. # Additional Changes - ensure keys for introspection and add session recipes. # Additional Context - Closes #11585 --------- Co-authored-by: Silvan <27845747+adlerhurst@users.noreply.github.com>
9 days ago
by muhlemmer
m
Succeeded
fix-benchmark-introspect
e6d0e219 chore(docs): fix cutoff handling to address missing docs in release 4.11 (#11600) Fixes failing pipelines, because in release 4.11 the app/docs folder is missing due to a potential cherry pick issue from the next branch
9 days ago
by muhlemmer
m
Succeeded
fix-benchmark-introspect
e6d0e219 Merge 6d175db23185736d34a920a5a9477772d1dd3b97 into 728a5f01580be770708da116868b2d29938137d2
9 days ago
by muhlemmer
m
Succeeded
fix-benchmark-introspect
338e0cad fix: ensure keys
12 days ago
by muhlemmer
m
Succeeded
fix-benchmark-introspect
338e0cad Merge 6c33226a6aed11489bb1538de294b7aeb9400c0c into 2a2d5392a3e466cc4cc6ae881a962f1cef0cd44e
12 days ago
by muhlemmer
m
Failed
feat-request-id
36dbf309 fix: add tests and fix doc comments for request ID interceptors (#11559) # Which Problems Are Solved PR review identified missing test coverage and documentation issues in the request ID interceptor implementation: - Request ID interceptors (HTTP, gRPC, Connect) lacked test coverage despite adding externally observable behavior - Doc comment incorrectly stated HTTP middleware was a "gPRC interceptor" - Inline comment incorrectly stated all HTTP requests use POST (only true for gRPC) - Typo "gPRC" instead of "gRPC" in gRPC interceptor doc comment # How the Problems Are Solved **Test Coverage** - Added comprehensive tests for HTTP middleware verifying header is set across status codes - Added tests for gRPC interceptor verifying header is set on success and error responses - Added tests for Connect interceptor verifying header on success and trailer metadata on errors - All tests validate UUID format and consistency between context and response metadata **Documentation Fixes** - Corrected HTTP log interceptor doc comment to reflect it's HTTP middleware, not gRPC - Removed misleading "gRPC always uses POST" comment from HTTP log interceptor - Fixed "gPRC" → "gRPC" typo in gRPC log interceptor # Additional Changes None # Additional Context Addresses review comments from https://github.com/zitadel/zitadel/pull/11509 <!-- START COPILOT CODING AGENT TIPS --> --- 💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey). --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: muhlemmer <5411563+muhlemmer@users.noreply.github.com> Co-authored-by: Tim Möhlmann <tim+github@zitadel.com>
14 days ago
by muhlemmer
m
Succeeded
feat-request-id
36dbf309 Merge 28efee153d336230b993d34840a1ee8d6a53dd65 into 319c46647606087741a8f5eecf29eec34f361a7c
14 days ago
by muhlemmer
m
Succeeded
copilot/sub-pr-11509
daf7054b fix: unit tests
14 days ago
by muhlemmer
m
Failed
remove-legacy-config
075dfae2 feat(instrumentation): remove legacy config (#11529) # Which Problems Are Solved - Legacy Log configuration in `cmd/initialise` causes nil pointer dereference after removing legacy config support # How the Problems Are Solved - Remove legacy Log field and `SetLogger()` call from `cmd/initialise/config.go` # Additional Changes None # Additional Context - Follow up on https://github.com/zitadel/zitadel/pull/11159 - Addresses review feedback on removing legacy instrumentation configuration --- 💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more [Copilot coding agent tips](https://gh.io/copilot-coding-agent-tips) in the docs. --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: muhlemmer <5411563+muhlemmer@users.noreply.github.com>
14 days ago
by muhlemmer
m
Previous page
Previous
Next
Next page