pivotoolz 2.3.0 → 2.4.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 648b707a351eb4f2b97c0a8a336f4bf7ac8efb96b9b619a903643d870839d136
-  data.tar.gz: d967f3097e9e3892aea0a4886e222a08780926afd200596aa9eec7215a56bc53
+  metadata.gz: 5e4d0adf8b4a31c7d0327a069606f4a16d4d59b1d50a89df72b3672a819b30b9
+  data.tar.gz: 5de0e5ddbf21bd0a74fd4a454dc3723482b5bc180c4e2cb465559996a25306ae
 SHA512:
-  metadata.gz: d9e1e27ad6af6380c1c4842a8c54459aa734d3d00c82aeb5d48197797c5034389a3832c92bfbbbd46012318caf2610c134452240b030cbb3bfc5c4fc644bf310
-  data.tar.gz: 1ecc3da31218e2b0b989f569b3d50f3715d3d934ef8aa33ce8efe804185d114bdbe57dbe9f0283435e15a98b7ec63e6a8521d5e4764a3e67b1750871308d176f
+  metadata.gz: 43c743777feacc4bcf4e36e31fa975b62134bc3db2f390ec6d0716fdbb144b5c2b691d3a852ff1c097cf0c2f13b9bf12693a21fcb1cffa4aa5c67e3220858ca9
+  data.tar.gz: 78dfcce32de3e457aa9d7fb5264a00a25150675eb72e278719521fe86e84440ef2cdfce61ff3b6a06cf70807d87041fb7312671494ed629a874a33cff7dc53ba

data/README.md

@@ -156,6 +156,29 @@ https://www.pivotaltracker.com/story/show/456
 Use with `post-slack-message` to post a message in a slack deployment channel
 with the list of stories that just got deployed.
 
+For a slack-compatible formatted message, add the `--json` flag.
+
+There are additional formatting flags if you want to see the name of the person who completed a story in the slack formatted message:
+`--owners` - Show name of person who completed the story as part of the message
+
+`--owners-footer` - Show name of person who completed the story as a footer (requires `--owners` flag)
+
+`--bold-owners` - Show name of person who completed the story in bold text (requires `--owners` flag)
+
+### `jira-stories-deployed`
+
+Similar to `stories-deployed`, but for Jira! Now you can use your favourite development workflow accelerator, even if your
+current team uses Jira!
+
+Simply define the following environment variables, and you're ready to go!
+
+```
+export JIRA_API_BASIC_AUTH_BASE64_ENCODED=BASE_64_ENCODED_username:password   # See https://developer.atlassian.com/server/jira/platform/basic-authentication/
+export JIRA_API_BASE_URL=https://YOUR_ORG.atlassian.net/rest/api/3/issue/
+export STORY_ID_REGEX=YOUR_STORY_ID_PATTERN_REGEX  # Falls back to [[:alpha:]]+-\d+ if not set
+```
+Use `jira-stories-deployed` just as you would `stories-deployed`.
+
 ### `post-slack-message`
 
 Post a message to a slack channel. You will need to [setup

data/exe/jira-stories-deployed

@@ -1,5 +1,7 @@
 #!/usr/bin/env ruby
 
+#encoding: utf-8
+
 require 'json'
 require 'ostruct'
 require 'uri'

data/exe/jira-story-ids-deployed

@@ -17,7 +17,7 @@ end
 commit_message_bodies = `git log --pretty="%h %s" #{commit_range}`.strip
 story_ids = commit_message_bodies.
   # TODO: Make this configurable
-  scan(/(DI-\d+|ST-\d+)/).
+  scan(/#{ENV['STORY_ID_REGEX'] || '[[:alpha:]]+-\d+'}/).
   flatten.
   compact.
   uniq

data/lib/pivotoolz/version.rb

@@ -1,3 +1,3 @@
 module Pivotoolz
-  VERSION = "2.3.0"
+  VERSION = "2.4.1"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: pivotoolz
 version: !ruby/object:Gem::Version
-  version: 2.3.0
+  version: 2.4.1
 platform: ruby
 authors:
 - Sufyan Adam
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2021-12-06 00:00:00.000000000 Z
+date: 2022-11-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rest-client
@@ -141,7 +141,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.2.3
+rubygems_version: 3.3.7
 signing_key:
 specification_version: 4
 summary: Tools to save you time when working with Pivotal Tracker stories