Working with VSTS personal branches

Reading This Manual

Copying all content from this file and pasting it at https://jbt.github.io/markdown-editor/ will not display images and gif animations since they are stored locally within the repository. It is strongly recommended to read this document inside Atom text editor using Ctrl + Shift + M to display the rendered preview.

Introduction

Use Git and VSTS to save your work and coordinate code changes across your team.

How to work with VSTS personal branches:

  1. Create a branch for the changes that you plan to make, and name it accordingly.
  2. Add your branch to the Post-commit build definition trigger.
  3. After working changes are committed, Push your branch to the remote repository.

1. Create a branch for the changes that you plan to make, and name it accordingly

Go to Code -> Branches. Click New branch and create branch under the following convention: [firstname].[lastname]. Select the created branch to work with it.

2. Add your branch to the Post-commit build definition trigger

Go to the Build and Release -> Build -> All Definitions -> Post-commit Build -> Edit -> Triggers. Add your branch to Branch Filters. Click Save and queue -> Save.

3. After working changes are committed, Push your branch to the remote repository

Share changes made in commits and branch using the push command. Push your branch to the remote repository, where Git takes the commits and adds them to an existing branch on the remote or creates a new branch with the same commits as your local branch.

If there are any conflicts between your local commits and the commits on the remote branch, you must first resolve these conflicts before you can push your changes. You should pull the changes from others first, resolve the conflicts and commit the changes, then reattempt the push.

Author: Dmitry Andreev

Leave a Comment