-
Notifications
You must be signed in to change notification settings - Fork 1
WorkFlow
We use Github Issues, and Pull Requests, in addition to Visual Studio Team Services (VSTS) for issue tracking.
Issues in Github are the over arching issue that is being described. This doesn't necessarily (but could) include all the steps to fix it. Once you create the Github Issue, a VSTS User Story will be created with the details that the issue was created with. Details such as who is assigned to it, the title, description, and more.
In VSTS, you can drag the user story to the current Iteration (on the left) that we are in. From there you can add tasks and use the board (tab on the top of the user story section) to move the tasks as they are completed.
You can add information and talk about a specific task when tagging others in the dialog. There is also a section for how long you expect the task to take, how long the task did take, and how much time you think is left to complete the task. You can use this to get a better idea for how long it takes you to complete tasks.
In the tasks board there are 3 columns that the tasks can be dragged to. New, Active, and Completed. These columns are fairly self explanatory. Once all the tasks have been completed, and the user story is completed, you can submit a pull request. When the pull request is finished, and the changes have been merged into master, you can move the user story to the completed column. You can also close the Github Issue and reference the pull request made.
When you start to work on a Github Issue, create a new branch for it. Then when you are finished, go to Github, Pull Requests, and select to make a new Pull Request. Fill out the information needed, and select the branch that you are using. When the pull request is approved, you or someone else can then click on the on the Rebase and Merge button. This will merge the commits to the master branch. Once complete you can safely delete the branch you created.