Merge branch 'develop' into feature/setze-standardwerte-von-inputrange

Author: deleonio

.github/workflows/benchmark.monitoring.yml

@@ -1,9 +1,7 @@
 name: Benchmark-Monitoring
 
 on:
-  push:
-    branches:
-      - develop
+  workflow_dispatch:
 
 concurrency:
   group: 'workflow-${{ github.workflow }}-${{ github.ref }}'

.github/workflows/benchmark.pr-check.yml

@@ -1,16 +1,18 @@
 name: Benchmark-PR-Check
 
 on:
-  pull_request:
+  workflow_dispatch:
+    inputs:
+      pr-number:
+        description: Pull request number to comment on
+        required: true
 
 concurrency:
   group: 'workflow-${{ github.workflow }}-${{ github.ref }}'
   cancel-in-progress: true
 
 jobs:
   benchmark:
-    # Skip this job when the base clone URL may be different from the head clone URL.
-    if: github.event.pull_request.head.repo.fork == false
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
@@ -31,12 +33,12 @@ jobs:
         with:
           body-includes: Hydration Benchmark Report
           comment-author: 'github-actions[bot]'
-          issue-number: ${{ github.event.pull_request.number }}
+          issue-number: ${{ github.event.inputs.pr-number }}
 
       - name: Post PR Comment
         uses: peter-evans/create-or-update-comment@v4
         with:
           body-path: packages/tools/benchmark-tests/benchmark-report.md
           comment-id: ${{ steps.fc.outputs.comment-id }}
           edit-mode: replace
-          issue-number: ${{ github.event.pull_request.number }}
+          issue-number: ${{ github.event.inputs.pr-number }}

packages/components/AGENTS.md

@@ -47,3 +47,12 @@ updating texts when the component is rerendered. Cache the value in a class
 property whose name starts with `translate` followed by the translation
 identifier, for example `translateSort` for `kol-sort` or `translateOrderBy`
 for `kol-order-by`.
+
+### Properties
+
+To make the components easier to learn, property names and their descriptions should be consistent across components. Therefore you should:
+
+- Use the same property name for attributes that serve the same purpose.
+- Whenever possible, use identical descriptions for identical property names.
+- Whenever possible, keep the types of identical property names the same.
+- Minimize the number of different properties, descriptions and types.