Git Workflows, Tools, and Uses

Learn about Git's workflows, tools, and uses.

We'll cover the following

Workflow

A developer workflow is a set of steps required to accomplish a particular task. There are workflows for adding new code to a codebase, testing, code reviews, and other tasks. Managing work in an SCMsource control management system is one of several workflows.

Git supports a number of common workflows. One Git workflow, based on branching, is called a feature branch workflow. A typical day in the life of a developer using a feature branch workflow might look like the following:

A developer arrives at work, starting their day, and then they:

  1. Open a task list, such as a kanban board.

  2. Pull a task off the list to complete.

  3. Update their local repository with work committed to the authoritative repository by other developers.

  4. Create a local feature branch (also called a topic branch) and switch their local repository to that new branch.

  5. Write the code to complete the feature specified in the task and commit that work to the feature branch.

  6. Upload the feature branch to the authoritative repository when the task is complete.

  7. Submit a request (called a pull request) through the authoritative repository system to have their code merged into the main branch.

  8. Start over from Step 2 with a new unfinished task while waiting for their request to be processed.

Get hands-on with 1400+ tech skills courses.