{"id":4718,"date":"2016-03-19T16:11:48","date_gmt":"2016-03-19T16:11:48","guid":{"rendered":"https:\/\/www.process.st\/templates\/git-workflow\/"},"modified":"2024-02-28T16:41:34","modified_gmt":"2024-02-28T16:41:34","slug":"git-workflow","status":"publish","type":"post","link":"https:\/\/www.process.st\/templates\/git-workflow\/","title":{"rendered":"Git Workflow"},"content":{"rendered":"
\n

Introduction <\/h2>\n
\n
\n <\/a>
\n <\/figure>\n<\/p><\/div>\n
\n

Your latest sprint is almost over and everything has been running smooth as butter; things are looking great! All you need to do is finish off your git workflow and publish that final, one-line update and then clock off for the evening.<\/p>\n

Aaaaaaaaand everything's broken.<\/p>\n

'...we all make mistakes. Some of those mistakes are unimportant, but some of them are expensive or dangerous<\/em>' - ISTQB<\/a><\/p>\n

Never fear! By following this template you can ensure that your git workflow will run smoothly every single time. From forking your repository to testing the living daylights out of your alterations, we here at Process Street<\/a> have the perfect executable checklist for any and all updates to your code.<\/p>\n

Let's get started!<\/p>\n<\/p><\/div>\n<\/section>\n

\n

Preparation: <\/h2>\n<\/section>\n
\n

Log in to your project management software <\/h2>\n
\n

The first thing you need to do in your git workflow is to see what features and bugs need working on. To this end, log in to your project management app<\/a><\/strong>. Remember to fill in the form fields<\/strong> below to record<\/strong> all of the basic data<\/strong> you'll need to refer to this later!<\/p>\n<\/p><\/div>\n

\n
\n
\n
\n
\n
\n
\n