5.7 Git Environment

Go To Top

Return to Development Environment

The development environment must include Git because the Phase 0 Baseline depends on a controlled Repository structure, change review, decisions on generated Artifacts, Baseline tagging, and reproducible collaboration.

Developers should configure Git before making Phase 0 changes. At a minimum, each developer should have a configured user name, email address, line-ending behaviour, and access to the shared Repository. The team should document any required branch-naming, commit-message, pull-request, review, or tagging conventions in the Git and Review Workflow section.

The Git environment should support clean review. Developers should avoid committing local build outputs, virtual environments, runtime logs, temporary files, editor caches, or machine-specific Configuration. The .gitignore file should protect the Repository from common accidental commits.

The team should use Git tags, branches, or release markers to identify important Phase 0 Baselines. When the team changes Repository layout, generated Artifact policy, Type definitions, scripts, Node patterns, containers, or acceptance criteria, the Git history should show that change clearly.