Branching

If you are working on a repository for a project and you need to implement a new feature, the first thing you usually do is grab the latest changes from the master or develop branch. Once all these changes have been pulled in, you create a feature branch. Most likely, your branch will have the same identifier as the ticket you are working on. For instance, if I have a ticket, identified as MARKETING-248, it will make sense to have a separate branch to match this ticket. Project management tools —if set up correctly— can integrate with git branches for better visibility.

You will clone the nobot-repo-1 repository from the previous lesson into your working directory and create a feature branch from the base branch, e.g. the master. You will only ask the user for a ticket ID and your script will automatically create a branch matching that ID.

Note: Just like in the previous lesson, first you will have to copy the contents of the config.example.json file and create a new config.json file. For convenience, this has ...