GIT:Workflow Examples

From Remain Software
Jump to navigation Jump to search

Overview of Setup Workflow for IBM i native sources

Before a developer can start developing native IBM i sources, the following setup workflow needs to run.

  1. TD/OMS: TD/OMS provides commands to copy native from source files to the IFS;
  2. GIT: The sources are pushed to a remote repository;
  3. TD/OMS: The matching TD/OMS Route is associated with the Git repository;
  4. TD/OMS: The route is marked as a special source route (additional actions take place while editing);

Overview of Setup Workflow for other IFS sources (PHP, JS, etc..)

Before a developer can start developing sources, the following setup workflow needs to run.

  1. GIT: The sources are pushed to a remote repository;
  2. TD/OMS: The matching TD/OMS Route is associated with the Git repository;

Overview of Setup Workflow for other NON-IFS sources (PHP, JS, etc..)

Before a developer can start developing sources, the following setup workflow needs to run.

  1. GIT: The sources are pushed to a remote repository;
  2. TD/OMS: The matching TD/OMS Application is associated with the Git repository;

Main Workflow

The TD/OMS Git workflow is based on the TD/OMS Task system. The main steps are:

  1. TD/OMS: The developer is assigned to a Task;
  2. TD/OMS: The developer clones the source repository;
  3. GUI: The developer imports the projects;
  4. GUI: The developer edits and commits sources;
  5. TD/OMS: The developer finishes the task;
  6. Git: The developer pushes the changes
  7. TD/OMS: The developer deploys the sources to the next environments;

Task Switching

The developer is able to work in teams or work on more than one Task.

  1. The developer switches to another Task
  2. The developer switches back to the original Task

Team Programming

The developer is able to work in teams of work on more than one Task.

  1. The developer starts working on a Task.
  2. The developer prepares a team repository
  3. The developer invites team members to work on the same Task
  4. The developer merges other changes in the local repositories
  5. The developer commits changes