6 Commits

Include renames

Author	SHA1	Message	Date
Thore CimbalandClaude Sonnet 5	8d46fb33d2	ci: use lockfile install instead of layered.sh, fix always-green gate ... layered.sh clones a branch-matching upstream matrix-js-sdk - on this fork that would override the deliberately pinned js-sdk from pnpm-lock.yaml (issue #12) with upstream develop, and it also needs jq which the node:20 job container lacks (the actual CI failure). Plain frozen-lockfile install matches the production docker build. Also replace the contains(needs.*.result, ...) gate check with explicit per-job checks: the object-filter syntax evaluated wrongly on Gitea/act, letting build-complete report success while build_ew had failed. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-30 12:00:00 +00:00
Thore CimbalandClaude Sonnet 5	71ac7c4346	ci: map runs-on to actual runner labels, trim jobs the runner can't serve ... Root cause found for jobs never starting: runs were created all along (visible in the Actions UI), but every job requested ubuntu-24.04 while builder-1 only offers ubuntu-latest, linux-build and win-wine - a label mismatch means jobs queue forever, invisible via the /actions/tasks API which only lists picked-up jobs. Mapped build/prepare/gate jobs to ubuntu-latest and the Linux desktop build to linux-build (electronuserland/builder image, amd64/static only - the only variant buildable on the single x86 runner). Removed jobs the runner cannot serve instead of letting them starve the queue: web+desktop playwright tests (need Docker-in-job and display setup, tracked as follow-up in issue #2) and the native-Windows desktop build (workflow assumes signtool/MSVC/PowerShell; the win-wine label awaits a dedicated wine-based workflow). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-30 12:00:00 +00:00
Thore CimbalandClaude Sonnet 5	f2abae85dd	ci: remove unused workflow_call trigger (Gitea Actions bug go-gitea/gitea#33238) ... push + workflow_call in the same on: block doesn't reliably fire push events on Gitea Actions 1.27 (reproducible upstream, closed as "not planned" - https://github.com/go-gitea/gitea/issues/33238). Nothing in this repo invokes build-and-test.yaml via workflow_call anymore after the workflow cleanup, so removing the trigger is a safe, targeted fix rather than a workaround. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-30 12:00:00 +00:00
Thore Cimbal	0f1d31021c	ci: add trigger-test note to force a real push event	2026-07-30 12:00:00 +00:00
Thore CimbalandClaude Sonnet 5	77ffeb4514	ci: reduce workflows to fork-relevant CI, fix upstream checkouts (Issue #2) ... Removed ~37 workflow files that are unmodified upstream tooling this fork doesn't use (Netlify, SonarCloud, Localazy, release-drafter/backport, GitHub issue-triage bots, npm-publish, Cloudflare Pages deploy, Docker push to ghcr.io/element-hq). Enabling Actions for this repo would have activated all of them simultaneously against a single-capacity shared runner - most would just fail loudly and starve the one job slot shared with other repos. Kept build-and-test.yaml (the actual comprehensive build+test+desktop workflow) and its build_desktop_*.yaml sub-workflows. Fixed: push trigger now targets `main` (was `staging`/`master`, neither of which exist here - push events never fired at all before), 4 checkout steps now check out this fork instead of element-hq/element-web, and removed the macOS desktop build job since the registered runner (builder-1) has no macOS label and would queue forever instead of failing cleanly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-07-30 12:00:00 +00:00
sorB	3da363517f	feat: show call participants in room list (Discord-style)	2026-05-10 14:25:35 +02:00