pivotoolz 2.3.0 → 2.4.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 648b707a351eb4f2b97c0a8a336f4bf7ac8efb96b9b619a903643d870839d136
-  data.tar.gz: d967f3097e9e3892aea0a4886e222a08780926afd200596aa9eec7215a56bc53
+  metadata.gz: 4dd31c5a6721ed081086c98c0a069f4a38a4c1dde54b170e446780da2773bdd4
+  data.tar.gz: b099cfa80fdc349cead72eaded1c036467f793feb063fa8d54672a94f789d481
 SHA512:
-  metadata.gz: d9e1e27ad6af6380c1c4842a8c54459aa734d3d00c82aeb5d48197797c5034389a3832c92bfbbbd46012318caf2610c134452240b030cbb3bfc5c4fc644bf310
-  data.tar.gz: 1ecc3da31218e2b0b989f569b3d50f3715d3d934ef8aa33ce8efe804185d114bdbe57dbe9f0283435e15a98b7ec63e6a8521d5e4764a3e67b1750871308d176f
+  metadata.gz: 929634a5713e90745ae1bc2cac413855af3dee6441092c3f010854bc4159461f08d38872d9a6faa25cb2bae23ae7fba7094d487d5edbdc9b6601319c9b602a6a
+  data.tar.gz: 6437d69d3b64ed6c9dd380e3fb0028b94a71af256e3142e3d92946fb73fd8bae5c580c98c2ec532d73b3a4b467d6e03f6048077875f1ebe254cbade96c33411d

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-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.0"
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: pivotoolz
 version: !ruby/object:Gem::Version
-  version: 2.3.0
+  version: 2.4.0
 platform: ruby
 authors:
 - Sufyan Adam
 autorequire:
 bindir: exe
 cert_chain: []
-date: 2021-12-06 00:00:00.000000000 Z
+date: 2022-01-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.2.22
 signing_key:
 specification_version: 4
 summary: Tools to save you time when working with Pivotal Tracker stories