Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Individual components can be connected to their own self contained repositories enabling commits, pushes, and pulls specific to the component repository.

Configuring a component as a self-contained Git repository means:

  • Component-Level Version Control: You can leverage the Git Workflow in the Translator to make commits, push, pull and merge changes with component repositories.

  • Holistic View: Commits are stored within the component project file in your Git Instance repository. Commits can be viewed on the Dashboard and Component Commit Histories.

  • Leverage Libraries: Sharing code across projects is made easier with libraries. These libraries can be stored within component repository projects as submodules.

  • Create Template Interfaces: Component’s with connected repositories can be stored in Collections and used as custom templates to streamline development of future projects.

  • Easier deployment Across Instances: You can import the component repository for use in other environments without the overhead of managing the full Git Instance repository.

  • No labels