Content
View differences
Updated by Oliver Günther almost 11 years ago
**As an** OP user
**I want to** have an abstract SCM repository interface
**So that** I can instrument repository creation, deletion and access changes from within the OpenProject user interface.
To provide a unified access to an unknown number of SCM implementations, we need an abstract interface (through the `Repository` model) to hide access to SCM adapters.
This will allow both core and plugin developers to implement actions when a repository is {created, deleted, updated} in the UI.
**I want to** have an abstract SCM repository interface
**So that** I can instrument repository creation, deletion and access changes from within the OpenProject user interface.
To provide a unified access to an unknown number of SCM implementations, we need an abstract interface (through the `Repository` model) to hide access to SCM adapters.
This will allow both core and plugin developers to implement actions when a repository is {created, deleted, updated} in the UI.