Development

This document provides a high-level guide for contributors working on the git-merged-branches codebase. It outlines the toolchain, development workflows, and project standards.

For information about automated release processes and CI/CD pipelines, see Release Management. For details about the system architecture and module organization, see Architecture.

Development Environment Overview

The project uses a modern TypeScript stack managed by pnpm package.json10 The toolchain is designed for high performance, utilizing tsdown for bundling and vitest for testing.

Development Toolchain Architecture

Sources: package.json27-44 tsconfig.json1-15 tsdown.config.ts1-7

Build System

The build process is managed by tsdown, which handles TypeScript compilation and bundling into a minified ES module format package.json3-39

• Output: The primary artifact is dist/index.mjs package.json27
• Configuration: The build includes a Shebang (#!/usr/bin/env node) to ensure CLI compatibility and executes publint to verify package exports tsdown.config.ts4-7

For details, see Build System.

Sources: tsdown.config.ts1-7 package.json39

Testing

Testing is performed using vitest. The test suite focuses on validating the output formatting logic and Git interaction orchestration package.json40-55

• Execution: Run npm run test to execute the suite once package.json40
• Focus: Tests ensure that branch lists and issue URLs are formatted correctly according to the user's package.json configuration.

For details, see Testing.

Sources: package.json40-55

Code Quality

The project maintains high code quality through a combination of TypeScript type checking and ESLint linting package.json41-44

• Linting: Uses neostandard with specific @stylistic overrides for double quotes and semicolon enforcement eslint.config.js1-25
• Type Safety: tsc is used in noEmit mode to validate type integrity without generating files package.json41 tsconfig.json10

For details, see Code Quality.

Sources: eslint.config.js1-25 package.json41-44

Dependency Management

pnpm is the required package manager package.json10 A key feature of the dependency strategy is the use of nolyfill overrides.

• Nolyfill Strategy: To keep the tool lightweight, many common utility polyfills (like array-includes or object.assign) are overridden with nolyfill versions package.json57-77
• Engine Requirements: The codebase targets Node.js version 22.18.0 or higher package.json36

For details, see Dependency Management.

Sources: package.json10-77 pnpm-lock.yaml7-25

Local Development Setup

To begin contributing, clone the repository and install dependencies using pnpm.

For details, see Local Development Setup.

Sources: package.json10-39