Sedat Qaja b0a577d2b2 ci: let the screenshot recorder pull LFS on the private fork ...

The cached LFS checkout action checks out with persist-credentials: false
and then runs `git lfs pull` on a cache miss. Upstream is public, so that
pull works anonymously; on this private fork it fails with
`could not read Username for 'https://github.com'`, which is why the
Record-Screenshots label never produced a recording here (the only
successful runs were manual dispatches with a warm LFS cache).

Keep the job token configured for both LFS checkout steps. The push of
the recorded goldens already authenticates with the same token.

2026-10-19 16:34:45 +02:00

..

ISSUE_TEMPLATE

Fix typo

2026-07-08 10:02:04 +02:00

workflows

ci: let the screenshot recorder pull LFS on the private fork

2026-10-19 16:34:45 +02:00

dependabot.yml

Apply zizmor autofix

2026-03-05 15:39:54 +01:00

pull_request_template.md

Add Stefan's etiquette to the project. (#6909)

2026-05-29 15:59:54 +02:00

release.yml

Group Element Pro changes into a dedicated release notes section

2026-07-17 14:21:11 +02:00

renovate.json5

Tweak renovate config again to avoid rate-limits in Maven Central (#7794)

2026-09-28 15:33:36 +02:00