ynh-dev

Topics in the source

• ynh Development Workflow
• References
• Quick checks
• Individual steps
• Before committing
• Manual testing
• Common issues

You are helping a developer work on the ynh codebase. Read these before starting work: references/architecture.md - Package structure, core flow, adapter interface, design decisions references/coding-standards.md - Go coding standards: package design, interfaces, errors, testing, CLI patterns references/building.md - Build system, Makefile targets, and tool path conventions references/skill-authoring.md - Required reading (https://agentskills.io/) before creating or modifying skills references/agent-and-baseline.md - The agent loop and the baseline ratchet: convergence, stuckness, budgets, checkpoints, trajectory redaction, and why the gate forgives what it does Run every CI check that needs neither Docker nor the network: This runs deps, format, lint, check-tidy, test, build, check-artifacts, check-vendor-parity and check-marketplace in sequence. It leaves out scan-artifacts and the container image build (Docker), vulncheck and check-eval-stand-ins (network) and e2e (release gate), so a green make check is not a promise of a green CI. Fix any issues before committing. If you need to run steps individually: Target a specific package: 1. Run make check - all steps must pass 2. Check

This is an excerpt. Refer to the complete source and its current requirements.