story_branch 0.2.11 → 0.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: 87dd3ed376746ad1ef5041b8163ca121b6c0e465
-  data.tar.gz: 76a8b44ef9a1d240c39f84c0a6f7ce8cbca7b561
+  metadata.gz: 601d26c296267a0ad82258cb4978d82a538e88b6
+  data.tar.gz: 3b667d1a51fb3a1a8ad509fb98a956c241e8edc2
 SHA512:
-  metadata.gz: a20f1ef3bb406a75c1c590765ce45802a9ce29adec86366132fcd69e29950c77110f1b762126c8fbca98751a201fad549535ceb5acfcef8e776490148e799b0d
-  data.tar.gz: 0af67bc5bc79e81e16b206ef799b643181aaea897797cf2e93bd96b097bfb3392c586f692f37789b8469c591a1762f3cfe73aa480338801a3d84b35cf88e25e0
+  metadata.gz: c1cdef1c858ccbfca16e4a79f98712eabfae71aa08aa6b8faed758eded648eae82df1c8d4ff7ec1af79b4f2ce8d9661f00cd0347048d14d18ac67adba7b5a130
+  data.tar.gz: 4a75f85aeea2b9a293378c5e05f0c258079c8d748f8bd553719372fe02aaf6d02e9e2d2a422024338641fd34287e8742a86383a516906fd933da1a70c0003b0c

data/.circleci/config.yml

@@ -0,0 +1,37 @@
+version: 2
+jobs:
+  build:
+    docker:
+       - image: circleci/ruby:2.4.1-node-browsers
+    working_directory: ~/story_branch
+    steps:
+      - checkout
+      - restore_cache:
+          keys:
+          - v1-dependencies-
+      - run:
+          name: install dependencies
+          command: |
+            bundle install --jobs=4 --retry=3 --path vendor/bundle
+      - save_cache:
+          paths:
+            - ./vendor/bundle
+          key: v1-dependencies-{{ checksum "Gemfile.lock" }}
+
+      - run:
+          name: run tests
+          command: |
+            mkdir -p /tmp/test-results
+
+            TEST_FILES="$(circleci tests glob "spec/**/*_spec.rb" | circleci tests split --split-by=timings)"
+
+            bundle exec rspec --format documentation \
+                              --format RspecJunitFormatter \
+                              --out /tmp/test-results/rspec.xml \
+                              -- $(sed -e 's/\n/\\n/' -e 's/ /\ /' <<< "${TEST_FILES}")
+
+      - store_test_results:
+          path: /tmp/test-results
+      - store_artifacts:
+          path: /tmp/test-results
+          destination: test-results

data/.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,12 @@
+Before submitting an issue, please be sure to update to the latest Gem version
+
+### Describe the steps to reproduce
+
+### What did you expect to happen?
+
+### What happened instead?
+
+Paste in any error messages using [code-fences](https://help.github.com/articles/creating-and-highlighting-code-blocks/)
+
+### Additional information
+

data/.gitignore

@@ -0,0 +1,3 @@
+.DS_Store
+story_branch-*.gem
+/.pairs

data/.rspec

@@ -0,0 +1,2 @@
+--color
+--format documentation

data/Gemfile

@@ -0,0 +1,6 @@
+source "https://rubygems.org"
+
+git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
+
+# Specify your gem's dependencies in story_branch.gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,94 @@
+PATH
+  remote: .
+  specs:
+    story_branch (0.3.0)
+      blanket_wrapper (~> 3.0)
+      git (~> 1.2)
+      levenshtein-ffi (~> 1.0)
+      pastel (~> 0.7.2)
+      rb-readline (~> 0.5)
+      thor (~> 0.20.0)
+      tty-command (~> 0.8.0)
+      tty-config (~> 0.2.0)
+      tty-pager (~> 0.11.0)
+      tty-prompt (~> 0.16.1)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    blanket_wrapper (3.0.2)
+      httparty
+      recursive-open-struct
+    diff-lcs (1.3)
+    equatable (0.5.0)
+    fakefs (0.14.2)
+    ffi (1.9.23)
+    git (1.4.0)
+    hitimes (1.2.6)
+    httparty (0.16.2)
+      multi_xml (>= 0.5.2)
+    levenshtein-ffi (1.1.0)
+      ffi (~> 1.9)
+    multi_xml (0.6.0)
+    necromancer (0.4.0)
+    pastel (0.7.2)
+      equatable (~> 0.5.0)
+      tty-color (~> 0.4.0)
+    rake (10.4.2)
+    rb-readline (0.5.5)
+    recursive-open-struct (1.1.0)
+    rspec (3.0.0)
+      rspec-core (~> 3.0.0)
+      rspec-expectations (~> 3.0.0)
+      rspec-mocks (~> 3.0.0)
+    rspec-core (3.0.4)
+      rspec-support (~> 3.0.0)
+    rspec-expectations (3.0.4)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.0.0)
+    rspec-mocks (3.0.4)
+      rspec-support (~> 3.0.0)
+    rspec-support (3.0.4)
+    strings (0.1.1)
+      unicode-display_width (~> 1.3.0)
+      unicode_utils (~> 1.4.0)
+    thor (0.20.0)
+    timers (4.1.2)
+      hitimes
+    tty-color (0.4.2)
+    tty-command (0.8.1)
+      pastel (~> 0.7.0)
+    tty-config (0.2.0)
+    tty-cursor (0.5.0)
+    tty-pager (0.11.0)
+      strings (~> 0.1.0)
+      tty-screen (~> 0.6.4)
+      tty-which (~> 0.3.0)
+    tty-prompt (0.16.1)
+      necromancer (~> 0.4.0)
+      pastel (~> 0.7.0)
+      timers (~> 4.0)
+      tty-cursor (~> 0.5.0)
+      tty-reader (~> 0.3.0)
+    tty-reader (0.3.0)
+      tty-cursor (~> 0.5.0)
+      tty-screen (~> 0.6.4)
+      wisper (~> 2.0.0)
+    tty-screen (0.6.4)
+    tty-which (0.3.0)
+    unicode-display_width (1.3.0)
+    unicode_utils (1.4.0)
+    wisper (2.0.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 1.16)
+  fakefs (~> 0.14)
+  rake (~> 10.0)
+  rspec (~> 3.0)
+  story_branch!
+
+BUNDLED WITH
+   1.16.2

data/{LICENCE → LICENSE.txt}

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2014 Jason Milkins, Gabe Hollombe, Rui Baltazar, Dominic Wong
+Copyright (c) 2018 Story Branch
 
 Permission is hereby granted, free of charge, to any person obtaining a copy of
 this software and associated documentation files (the "Software"), to deal in

data/README.md

@@ -2,93 +2,112 @@
 
 # Story Branch
 
-A small collection of tools for working with git branches and Pivotal
-Tracker stories. `git story`, `git finish`, `git start` and `git
-unstart`.
+Story branch is a CLI application that interacts with Pivotal Tracker at the
+at the moment. It allows you to start and un-start stories as well as creating
+branches based on the story name and id and have a final commit message marking
+the story as Finished.
 
-### Commentary
+## Installing
 
-`git story`: Creates a git branch with automatic reference to a
-Pivotal Tracker Story. It will get started stories from your active
-project.  You can enter text and press TAB to search for a story
-name, or TAB to show the full list. It will then suggest an editable
-branch name. When the branch is created the `story_id` will
-be appended to it.
+Install the gem:
 
-e.g. `my-story-name-1234567`
+    gem install story_branch
 
-`git finish`: Creates a git commit message for the staged changes.
+## Usage
 
-e.g: `[Finishes #1234567] My story name`
+You should run story_branch from the git/project root folder.
 
-You must stage all changes (or stash them) first. Note the commit will not
-be pushed.  Note: You'll be able to bail out of the commit.
+## Commands available
 
-`git start`: Start a story in Pivotal Tracker from the terminal.
-It'll get all unstarted stories in your current project.  You can
-enter text and press TAB to search for a story name, or TAB to show
-the full list.
+You can see all the commands available by running
 
-`git unstart`: Unstart a story in Pivotal Tracker from the terminal.
-It'll get all started stories in your current project.  You can
-enter text and press TAB to search for a story name, or TAB to show
-the full list.
+```
+$ story_branch -h
+
+Commands:
+  story_branch add             # Add a new story branch configuration
+  story_branch create          # Create branch from estimated stories in pivotal tracker
+  story_branch finish          # Creates a git commit message for the staged changes with a [Finishes] tag
+  story_branch help [COMMAND]  # Describe available commands or one specific command
+  story_branch migrate         # Migrate old story branch configuration to the new format
+  story_branch start           # Mark an estimated story as started in Pivotal Tracker
+  story_branch unstart         # Mark a started story as un-started in Pivotal Tracker
+  story_branch version         # story_branch gem version
+```
 
-### Installing
+## Settings
 
-Install the gem:
+Story branch has a command available that will help you creating the configurations
+for the projects, but essentially you'll be asked for the pivotal tracker project id and your api key.
 
-    gem install story_branch
+The project id you can get it easily from the url when viewing the project.
 
-#### Settings
+The api key you can get it from your account settings.
 
-You can have your settings set either on a `.story_branch` file
-or in environment variables.
+### .story_branch files
 
-The `.story_branch` files have priority over environment variables so if you set both,
-the configuration within `.story_branch` will be the one used.
-Also, the `.story_branch` file inside a project directory has priority over the global one.
+When configuring story branch, it will create two .story_branch.yml files: one in
+your home folder (`~/`) and one in your project's root (`./`).
+The one in your home folder will be used to store the different project's configurations
+such as which api key to use. This is done so you don't need to commit your
+api key to the repository but still be able to use different keys in case you
+have different accounts.
 
-The settings will be loaded firstly from local config file, if not found then from global
-config file and ultimately from the environment variables. If none are found, an error
-will be thrown.
+The one in your project root will keep a reference to the project configuration.
+For now, this reference is the project id. This file can be safely committed to
+the repository and shared amongst your co-workers.
 
-This means that you can have a globally set api key and for each project using Pivotal Tracker
-have a local config inside the project folder.
-E.g.
+## Migrating
 
-```
-$ cat ~/.story_branch
-api: your_API_key_that_you_get_from_pivotal_tracker
+### Old configuration
 
-$ cat ~/your_project_dir/.story_branch
-project: 123123
-```
+If your were using story branch before there are some small changes on the way the
+tool works. But worry not, we've written a command that allows you to migrate your
+configuration. Running
 
-In case you prefer to use environment variables, you can set
-`PIVOTAL_API_KEY` to your pivotal tracker api key and set
-`PIVOTAL_PROJECT_ID` to your project id.
+`$ story_branch migrate`
 
-#### .story_branch file
+will grab your existing configuration and convert it into the new format. The only
+thing you'll need to provide is the project name reference.
 
-A YAML file with either/both of:
+### Old commands
 
-    api: YOUR.PIVOTAL.API.KEY.STRING
-    project: YOUR.PROJECT.ID.NUMBER
+Story branch was built providing a set of bin commands such as `git-story`, `git-finish`, `git-start` and `git-unstart`. These will be available still as
+we try as much as possible to keep the updates retro-compatible, but are nothing
+more than an alias for the CLI commands as follow:
 
-Can be saved to `~/` or `./` (ie. your project folder)
+- `git-story` runs `story_branch create`
+- `git-finish` runs `story_branch finish`
+- `git-start` runs `story_branch start`
+- `git-unstart` runs `story_branch unstart`
 
-### Usage
+## Commentary
 
-You run story_branch from the git/project root folder.
+`story_branch create`: Creates a git branch with automatic reference to a
+Pivotal Tracker Story. It will get started stories from your active
+project. You can enter text and press TAB to search for a story
+name, or TAB to show the full list. It will then suggest an editable
+branch name. When the branch is created the `story_id` will
+be appended to it.
+
+e.g. `my-story-name-1234567`
 
-`git story`, `git start` and `git unstart` are run interactively and
-will display a list of stories to work with.
+`story_branch finish`: Creates a git commit message for the staged changes.
 
-`git finish` will scan the current branch name for a story id (as its
-suffix) and if a valid, active story is found on pivotal tracker it
-will create a commit with a message to trigger pivotal's git
-integraton features.
+e.g: `[Finishes #1234567] My story name`
+
+You must stage all changes (or stash them) first. Note the commit will not
+be pushed. Note: You'll be able to bail out of the commit.
+
+`story_branch start`: Start a story in Pivotal Tracker from the terminal.
+It'll get all un-started stories in your current project. You can
+enter text and press TAB to search for a story name, or TAB to show
+the full list.
+
+`story_branch unstart`: Un-start a story in Pivotal Tracker from the terminal.
+It'll get all started stories in your current project. You can
+enter text and press TAB to search for a story name, or TAB to show
+the full list.
 
 ## Contributing
 

data/Rakefile

@@ -0,0 +1,6 @@
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec

data/exe/git-finish

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+
+`story_branch finish`

data/exe/git-start

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+
+`story_branch start`

data/exe/git-story

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+
+`story_branch create`

data/exe/git-unstart

@@ -0,0 +1,3 @@
+#!/usr/bin/env ruby
+
+`story_branch unstart`

data/exe/story_branch

@@ -0,0 +1,18 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+lib_path = File.expand_path('../lib', __dir__)
+$:.unshift(lib_path) if !$:.include?(lib_path)
+require 'story_branch/cli'
+
+Signal.trap('INT') do
+  warn("\n#{caller.join("\n")}: interrupted")
+  exit(1)
+end
+
+begin
+  StoryBranch::CLI.start
+rescue StoryBranch::CLI::Error => err
+  puts "ERROR: #{err.message}"
+  exit 1
+end

data/lib/story_branch.rb

@@ -1,480 +1,5 @@
-# Name: story branch
-#
-# Authors: Jason Milkins <jason@opsmanager.com>
-#          Rui Baltazar <rui.p.baltazar@gmail.com>
-#          Dominic Wong <dominic.wong.617@gmail.com>
-#          Ranhiru Cooray <ranhiru@gmail.com>
-#          Gabe Hollombe <gabe@neo.com>
-#
-# Version: 0.2.9
-#
-# ## Description
-# A small collection of tools for working with git branches and Pivotal
-# Tracker stories. `git story`, `git finish`, `git start` and `git
-# unstart`.
-#
-# ### Commentary
-#
-# `git story`: Creates a git branch with automatic reference to a
-# Pivotal Tracker Story. It will get started stories from your active
-# project.  You can enter text and press TAB to search for a story
-# name, or TAB to show the full list. It will then suggest an editable
-# branch name. When the branch is created the `story_id` will
-# be appended to it.
-#
-# e.g. `my-story-name-1234567`
-#
-# `git finish`: Creates a git commit message for the staged changes.
-#
-# e.g: `[Finishes #1234567] My story name`
-#
-# You must stage all changes (or stash them) first. Note the commit will not
-# be pushed.  Note: You'll be able to bail out of the commit.
-#
-# `git start`: Start a story in Pivotal Tracker from the terminal.
-# It'll get all unstarted stories in your current project.  You can
-# enter text and press TAB to search for a story name, or TAB to show
-# the full list.
-#
-# `git unstart`: Unstart a story in Pivotal Tracker from the terminal.
-# It'll get all started stories in your current project.  You can
-# enter text and press TAB to search for a story name, or TAB to show
-# the full list.
-#
-# ### Installing
-#
-# Install the gem:
-#
-#     gem install story_branch
-#
-# #### Settings
-#
-# You must have a `PIVOTAL_API_KEY` environment variable set
-# to your Pivotal api key, plus either a `.story_branch` file or
-# `PIVOTAL_PROJECT_ID` environment variable set. Note, values in
-# `.story_branch` will override environment variable settings.
-#
-# #### .story_branch file
-#
-# A YAML file with either/both of:
-#
-#     api: YOUR.PIVOTAL.API.KEY.STRING
-#     project: YOUR.PROJECT.ID.NUMBER
-#
-# Can be saved to `~/` or `./` (ie. your project folder)
-#
-# ### Usage
-#
-# You run story_branch from the git/project root folder.
-#
-# `git story`, `git start` and `git unstart` are run interactively and
-# will display a list of stories to work with.
-#
-# `git finish` will scan the current branch name for a story id (as its
-# suffix) and if a valid, active story is found on pivotal tracker it
-# will create a commit with a message to trigger pivotal's git
-# integraton features.
-#
-# ## Contributing
-#
-# All pull requests are welcome and will be reviewed.
-#
-# Code:
-
-require 'byebug'
-require 'yaml'
-require 'blanket'
-require 'rb-readline'
-require 'readline'
-require 'git'
-require 'levenshtein'
-
-trap('INT') { exit }
+require 'story_branch/version'
 
 module StoryBranch
-  class Main
-    ERRORS = {
-      'Stories in the started state must be estimated.' =>
-      "Error: Pivotal won't allow you to start an unestimated story"
-    }
-
-    PIVOTAL_CONFIG_FILES = ['.story_branch', "#{ENV['HOME']}/.story_branch"]
-
-    attr_accessor :p
-
-    def initialize
-      @p = PivotalUtils.new
-      @p.api_key = config_value 'api', 'PIVOTAL_API_KEY'
-      @p.project_id = config_value 'project', 'PIVOTAL_PROJECT_ID'
-      exit unless @p.valid?
-    end
-
-    def unauthorised_message
-      $stderr.puts 'Pivotal API key or Project ID invalid'
-    end
-
-    def create_story_branch
-      begin
-        puts 'Connecting with Pivotal Tracker'
-        @p.get_project
-        puts 'Getting stories...'
-        stories = @p.display_stories :started, false
-        if stories.length < 1
-          puts 'No stories started, exiting'
-          exit
-        end
-        story = @p.select_story stories
-        if story
-          @p.create_feature_branch story
-        end
-      rescue Blanket::Unauthorized
-        unauthorised_message
-        return nil
-      end
-    end
-
-    def pick_and_update filter, hash, msg, is_estimated
-      begin
-        puts 'Connecting with Pivotal Tracker'
-        @p.get_project
-        puts 'Getting stories...'
-        stories = @p.filtered_stories_list filter, is_estimated
-        story = @p.select_story stories
-        if story
-          result = @p.story_update story, hash
-          fail result.error if result.error
-          puts "#{story.id} #{msg}"
-        end
-      rescue Blanket::Unauthorized
-        unauthorised_message
-        return nil
-      end
-    end
-
-    def story_start
-      pick_and_update(:unstarted, { current_state: 'started' }, 'started', true)
-    end
-
-    def story_unstart
-      pick_and_update(:started, { current_state: 'unstarted' }, 'unstarted', false)
-    end
-
-    def story_estimate
-      # TODO: estimate a story
-    end
-
-    def story_finish
-      begin
-        puts 'Connecting with Pivotal Tracker'
-        @p.get_project
-
-        unless @p.is_current_branch_a_story?
-          puts "Your current branch: '#{GitUtils.current_branch}' is not linked to a Pivotal Tracker story."
-          return nil
-        end
-
-        if GitUtils.has_status? :untracked or GitUtils.has_status? :modified
-          puts 'There are unstaged changes'
-          puts 'Use git add to stage changes before running git finish'
-          puts 'Use git stash if you want to hide changes for this commit'
-          return nil
-        end
-
-        unless GitUtils.has_status? :added or GitUtils.has_status? :staged
-          puts 'There are no staged changes.'
-          puts 'Nothing to do'
-          return nil
-        end
-
-        puts 'Use standard finishing commit message: [y/N]?'
-        commit_message = "[Finishes ##{GitUtils.current_branch_story_parts[:id]}] #{StringUtils.undashed GitUtils.current_branch_story_parts[:title]}"
-        puts commit_message
-
-        if gets.chomp!.downcase == 'y'
-          GitUtils.commit commit_message
-        else
-          puts 'Aborted'
-        end
-      rescue Blanket::Unauthorized
-        unauthorised_message
-        return nil
-      end
-    end
-
-    def config_value key, env
-      PIVOTAL_CONFIG_FILES.each do |config_file|
-        if File.exists? config_file
-          pivotal_info = YAML.load_file config_file
-          return pivotal_info[key] if pivotal_info[key]
-        end
-      end
-      value ||= env_required env
-      value
-    end
-
-    def env_required var_name
-      if ENV[var_name].nil?
-        $stderr.puts "$#{var_name} must be set or in .story_branch file"
-        return nil
-      end
-      ENV[var_name]
-    end
-
-  end
-
-  class StringUtils
-
-    def self.dashed s
-      s.tr(' _,./:;+&', '-')
-    end
-
-    def self.simple_sanitize s
-      strip_newlines (s.tr '\'"%!@#$(){}[]*\\?', '')
-    end
-
-    def self.normalised_branch_name s
-      simple_sanitize((dashed s).downcase).squeeze('-')
-    end
-
-    def self.strip_newlines s
-      s.tr "\n", '-'
-    end
-
-    def self.undashed s
-      s.gsub(/-/, ' ').capitalize
-    end
-
-  end
-
-  class GitUtils
-    def self.g
-      Git.open '.'
-    end
-
-    def self.is_existing_branch? name
-      branch_names.each do |n|
-        if Levenshtein.distance(n, name) < 3
-          return true
-        end
-        existing_branch_name = n.match(/(.*)(-[1-9][0-9]+$)/)
-        if existing_branch_name
-          levenshtein_distance = Levenshtein.distance existing_branch_name[1], name
-          if levenshtein_distance < 3
-            return true
-          end
-        end
-      end
-      return false
-    end
-
-    def self.is_existing_story? id
-      branch_names.each do |n|
-        branch_id = n.match(/-[1-9][0-9]+$/)
-        if branch_id
-          if branch_id.to_s == "-#{id}"
-            return true
-          end
-        end
-      end
-      false
-    end
-
-    def self.branch_names
-      g.branches.map(&:name)
-    end
-
-    def self.current_branch
-      g.current_branch
-    end
-
-    def self.current_story
-      current_branch.match(/(.*)-(\d+$)/)
-    end
-
-    def self.current_branch_story_parts
-      matches = current_story
-      if matches.length == 3
-        { title: matches[1], id: matches[2] }
-      else
-        nil
-      end
-    end
-
-    def self.create_branch name
-      g.branch(name).create
-      g.branch(name).checkout
-    end
-
-    def self.status_collect status, regex
-      status.select{|e|
-        e.match(regex)
-      }.map{|e|
-        e.match(regex)[1]
-      }
-    end
-
-    def self.status
-      modified_rx  = /^ M (.*)/
-      untracked_rx = /^\?\? (.*)/
-      staged_rx    = /^M  (.*)/
-      added_rx     = /^A  (.*)/
-      status = g.lib.send(:command, 'status', '-s').lines
-      return nil if status.length == 0
-      {
-        modified:  status_collect(status, modified_rx),
-        untracked: status_collect(status, untracked_rx),
-        added:     status_collect(status, added_rx),
-        staged:    status_collect(status, staged_rx)
-      }
-    end
-
-    def self.has_status? state
-      return false unless status
-      status[state].length > 0
-    end
-
-    def self.commit message
-      g.commit(message)
-    end
-
-  end
-
-  class PivotalUtils
-    API_URL = 'https://www.pivotaltracker.com/services/v5/'
-    attr_accessor :api_key, :project_id
-
-    def valid?
-      !@api_key.nil? && !@project_id.nil?
-    end
-
-    def api
-      fail 'API key must be specified' unless @api_key
-      Blanket.wrap API_URL, headers: { 'X-TrackerToken' => @api_key }
-    end
-
-    def get_project
-      fail 'Project ID must be set' unless @project_id
-      api.projects(@project_id.to_i)
-    end
-
-    def story_accessor
-      get_project.stories
-    end
-
-    def is_current_branch_a_story?
-      GitUtils.current_story and
-        GitUtils.current_story.length == 3 and
-        filtered_stories_list(:started, true)
-        .map(&:id)
-        .include? GitUtils.current_story[2].to_i
-    end
-
-    def story_from_current_branch
-      story_accessor.get(GitUtils.current_story[2].to_i) if GitUtils.current_story.length == 3
-    end
-
-    # TODO: Maybe add some other predicates
-    # - Filtering on where a story lives (Backlog, IceBox)
-    # - Filtering on labels
-    # as the need arises...
-    #
-    def filtered_stories_list state, estimated
-      options = { with_state: state.to_s }
-      stories = [* story_accessor.get(params: options).payload]
-      if estimated
-        stories.select do |s|
-          s.story_type == 'bug' || s.story_type == 'chore' ||
-            (s.story_type == 'feature' && s.estimate && s.estimate >= 0)
-        end
-      else
-        stories
-      end
-    end
-
-    def display_stories state, estimated
-      filtered_stories_list(state, estimated).each {|s| puts one_line_story s }
-    end
-
-    def one_line_story s
-      "#{s.id} - #{s.name}"
-    end
-
-    def select_story stories
-      story_texts = stories.map{|s| one_line_story s }
-      puts 'Leave blank to exit, use <up>/<down> to scroll through stories, TAB to list all and auto-complete'
-      story_selection = readline('Select a story: ', story_texts)
-      return nil if story_selection == '' or story_selection.nil?
-      story = stories.select{|s| story_matcher s, story_selection }.first
-      if story.nil?
-        puts "Not found: #{story_selection}"
-        return nil
-      else
-        puts "Selected : #{one_line_story story}"
-        return story
-      end
-    end
-
-    def story_update story, hash
-      get_project.stories(story.id).put(body: hash).payload
-    end
-
-    def story_matcher story, selection
-      m = selection.match(/^(\d*) /)
-      return false unless m
-      id = m.captures.first
-      return story.id.to_s == id
-    end
-
-    def create_feature_branch story
-      dashed_story_name = StringUtils.normalised_branch_name story.name
-      feature_branch_name = nil
-      puts "You are checked out at: #{GitUtils.current_branch}"
-      while feature_branch_name == nil or feature_branch_name == ''
-        puts 'Provide a new branch name... (TAB for suggested name)' if [nil, ''].include? feature_branch_name
-        feature_branch_name = readline('Name of feature branch: ', [dashed_story_name])
-      end
-      feature_branch_name.chomp!
-      if validate_branch_name feature_branch_name, story.id
-        feature_branch_name_with_story_id = "#{feature_branch_name}-#{story.id}"
-        puts "Creating: #{feature_branch_name_with_story_id} with #{GitUtils.current_branch} as parent"
-        GitUtils.create_branch feature_branch_name_with_story_id
-      end
-    end
-
-    # Branch name validation
-    def validate_branch_name name, id
-      if GitUtils.is_existing_story? id
-        puts "Error: An existing branch has the same story id: #{id}"
-        return false
-      end
-      if GitUtils.is_existing_branch? name
-        puts 'Error: This name is very similar to an existing branch. Avoid confusion and use a more unique name.'
-        return false
-      end
-      unless valid_branch_name? name
-        puts "Error: #{name}\nis an invalid name."
-        return false
-      end
-      true
-    end
-
-    def valid_branch_name? name
-      # Valid names begin with a letter and are followed by alphanumeric
-      # with _ . - as allowed punctuation
-      valid = /[a-zA-Z][-._0-9a-zA-Z]*/
-      name.match valid
-    end
-
-    def readline prompt, completions=[]
-      # Store the state of the terminal
-      RbReadline.clear_history
-      if completions.length > 0
-        completions.each {|i| Readline::HISTORY.push i}
-        RbReadline.rl_completer_word_break_characters = ''
-        Readline.completion_proc = proc { |s| completions.grep(/#{Regexp.escape(s)}/) }
-        Readline.completion_append_character = ''
-      end
-      Readline.readline(prompt, false)
-    end
-  end
+  # Your code goes here...
 end