threadnet-call/.github/PULL_REQUEST_TEMPLATE.md at e2b46ee93765bf41b6cbf5a5bb2882ef6215f5ed - threadnet-call - Gitea: Git with a cup of tea

sorb/threadnet-call

Files

T

Thore CimbalandClaude Fable 5 8fb630cfb3 ci: GitLab-Pipeline - build_embedded + manueller npm-Publish nach rohana (threadnet-call#1)

Registry-Entscheidung evidenzbasiert: das Package ist pnpm-Dependency von
ThreadNet-Webs apps/web, der Lockfile pinnt die Tarball-URL auf rohana -
Registry bleibt dort. Publish-Auth ueber CI-Variable GITEA_NPM_TOKEN statt
lokaler Klartext-.npmrc.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-31 12:00:00 +00:00

1.4 KiB

Raw Blame History

Important

Features and UI changes require a pre-approved issue. Every PR must have a linked issue that a maintainer has reviewed and approved before you started writing code. PRs that don't meet this requirement will not be reviewed. See CONTRIBUTING.md for ElementCall decided for this approach.

Content

Motivation and context

Screenshots / GIFs

Tests

Step 1
Step 2
Step ...

Checklist

A linked, pre-approved issue exists for this feature or UI change.
I have read CONTRIBUTING.md in full.
Pull request includes screenshots or videos for any UI changes.
Tests written for new code (and existing touched code where feasible).
Linter and other CI checks pass.
I have licensed the changes to Element by completing the Contributor License Agreement (CLA)