====== 17.1 Repository Initialisation ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:17-git-and-review-workflow:start | Return to Git and Review Workflow ]]

The team should initialize the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] in a controlled way. Repository initialization should create the approved directory structure, Baseline files, ignore rules, documentation entry points, script locations, Configuration locations, placeholder directories, and other resources needed for the Phase 0 [[dido:99_annexes:annex-b-terms-and-definitions:b:baseline|Baseline]].

Repository initialization should include:

  - Repository root identification.
  - Approved top-level directory structure.
  - ''.gitignore'' file.
  - ''README.md'' file.
  - Initial documentation locations.
  - Script directories.
  - [[dido:99_annexes:annex-b-terms-and-definitions:i:idl|IDL]] source directory.
  - Generated [[dido:99_annexes:annex-b-terms-and-definitions:a:artifact|Artifact]] directory.
  - [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configuration]] directory.
  - Test directory.
  - [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|Evidence]] and log locations.
  - Container definition locations.
  - Checklist instance locations, where applicable.

The ''prepareGitRepository.sh'' script may support Repository initialization, but it should not hide the Repository rules. The handbook, README, and Repository documentation should explain the intended structure.

The Repository should avoid empty directories that Git cannot track unless the team adds controlled marker files, such as ''.gitkeep'', with a documented reason. The team should not use marker files as substitutes for real content once the relevant directory has governed Artifacts.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>