DepCharge User Stories

One Dependency per repo

(Target Use Case). All repos are downloaded and added to the path automatically when the DepCharge script is manually run in the project directory.

Multiple Dependencies per repo

Treat multiple packages within a repo as dependencies. Automatically setup paths. The use case is to support the refactoring process of extracting a utility package from an existing project package, without REQUIRING a new repository to be created. This flexibility will help with creating deliveries.

Dependency in folder at relative file path

Allows support independent from access to git repositories. Works without git installed.

Dependencies in zip file at relative file path

Aids code delivery to customers, for example. The goal is to leave infrastructure intact as appropriate for maintaining trackability to version control.

• Simple installation

• When we aggregate repos into a zip, we do not want to loose the traceability back to the version control. Significant manual modification is unacceptable.

• works without git installed