Developer Tools

Downloads GitHub Processes Pull Request Template Bug Report Template Feature Request Template Branching Strategy (clean, professional, simple) Keep branching rules simple. We don’t want a small team getting lost in GitFlow complexity. We use a lightweight GitFlow Hybrid: Branch Main develop feature/* release/x.y.z hotfix/* Purpose production integration for next release one task, one PR stabilizing next release emergency production fixes Lifetime forever forever short-lived short-lived short-lived This Git strategy ensures: Clean and predictable release flow Fast onboarding of new developers Safe integration of features Clear testing stages Zero long-lived personal branches Automatic cleanup of merged branches The 10 point strategy is intentionally simple, avoiding unnecessary complexity. Permanent Branches Main: Always production-ready Only updated via PR from: release/x.y.z hotfix/* develop: Integration branch All features are merged here Forms basis of future release candidates Temporary Branch Types feature/[summary] For individual tasks, e.g: feature/add_vessel_notes feature/update_engine_form_validation feature/new_pdf_renderer Rules: Created from develop PR must target

Dev Team – Culture & Expectations This document defines how we work as engineers, how we communicate, how we treat each other, and what is expected of every contributor to our codebase. Vessel Vanguard’s engineering team builds software used by vessel owners, captains, and operations teams who rely on accuracy, reliability, and practical workflows. Our job is to deliver high-quality, stable, predictable software that maritime professionals trust. We are a small team with big impact — which means clarity, ownership, and consistency matter more than anything. Our Engineering Values Reliability First: We write code that works — today and in six months. Clarity Over Cleverness: Readable code > fancy code. A new developer should understand your PR with zero explanation. Continuous Improvement: We look for ways to improve process, quality, and team experience. Leave Things Better Than You Found Them: You don’t need to fix everything — just one small