ワンクリックで
codeownership
// Maintain CODEOWNERS file and team specific directories. Use when working with "**/team-*/**" file structure or to split an old file into team-specific parts
// Maintain CODEOWNERS file and team specific directories. Use when working with "**/team-*/**" file structure or to split an old file into team-specific parts
| name | codeownership |
| description | Maintain CODEOWNERS file and team specific directories. Use when working with "**/team-*/**" file structure or to split an old file into team-specific parts |
[foo].ts into [foo]/team-[name]/*.ts/shared/feature-flags/src/flags/ contains team-coin-integration, team-engagement, team-live-devices, etc.
CODEOWNERS defines the owner for each of these:
**/team-coin-integration/ @ledgerhq/coin-integration
**/team-engagement/ @ledgerhq/engagement
**/team-live-devices/ @ledgerhq/live-devices
Create a pull request with proper description, changeset, and all required elements
Guided feature development with codebase understanding and architecture focus
Write unit and integration tests for Ledger Wallet apps. Use for Jest tests (Desktop/Mobile), MSW handlers and testing best practices. Applies to "*.test.*", "*.spec.*", "**/tests/**", "**/__tests__/**", "**/__integrations__/**", "**/jest-setup*"
Coin-specific families logic must live in families/. Generic UI uses the families contract only (no if (family === "evm") in shared code). Use this guidance for work in "**/families/**", "**/mvvm/**", "**/renderer/**" and "**/screens/**".
Prefer Set.has() over Array.includes() for constant allowlists/blocklists. Read this when reviewing or writing membership checks in TypeScript files.
Git workflow and commit conventions for Ledger Wallet