A repository is a central location for storing source code and connecting it to the pipeline that builds, tests, and deploys software. Keeping code near pipeline code makes incremental development, shared work, and rapid feedback more practical. section 2.4 section 2.6
A practical repository workflow includes:
- Create a hosted repository, install Git, and connect the local directory with git init and git remote add origin. section 2.4
- Keep onboarding notes, release milestones, tests, and deployment targets in the repository so development can proceed in small, demonstrable increments. section 2.0
- Use scripts and tools around the repository to make developer and system environments uniform and automate recurring tasks. section 2.6
A small repository plan
A hello API repository can begin with a README listing a one-day release: onboarding documentation, a simple API response, unit tests, and a deployment beyond the developer’s machine. Later milestones can add translation endpoints, short-term storage, and integration with an existing service. section 2.0
Listing 2.1 README.md
# Hello API ## Release Milestones ### V0 (1 day) - [ ] Onboarding Documentation - [ ] Simple API response (hello world!) - [ ] Unit tests - [ ] Running somewhere other than the dev machine ### V1 (7 days) - [ ] Create translation endpoint - [ ] Store translations in short-term storage - [ ] Call existing service for translation - [ ] Move towards long-term storage
Inspect the milestone-driven README used to turn a repository into a visible plan for incremental delivery. section 2.0
