git-maintain 0.2.0 → 0.2.2.pre.1.gc26b949

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 216d826fe15a57ca1d457a39bb20368b64eca217ac4f7a5b2119af8b7d775336
-  data.tar.gz: 9ad2d84895fe7116dcf6b96fcca0b1b217692a2376affa2e41306ac38691902c
+  metadata.gz: 080f301f3346a9365b503ae837b917269c1e8b81fc300e3f3ee0416acc891f9f
+  data.tar.gz: 37a7423b5fa56c59fdda3c654123a7466e53938e9c1fc2a2cc57636b984b6bd9
 SHA512:
-  metadata.gz: 3395184297ab04b2f13644bd3cba9bdbb45841bf0d96742a8726f3ff58e9b991895f7f9a029445a5bdabae481286c2e89462cc238cd525405ef1da0a35fb3e9f
-  data.tar.gz: 5b7f168f776ff74203c1e5e609d365e62151bb19c21514faf17b5e80adaed38f4c5349adaf08c8be4feda4b5703578a7126ee71467c2beafb43b01d04fe0be64
+  metadata.gz: d7a8bb88151eaf701bbaadbe493d4240f37e03a892a958f32c38b94f0f43b1ee8b5846ca6c27802f25822e5389df013e8ac20a8025fbd1def71830a13bf290f9
+  data.tar.gz: 7c5d0142287997ae675183ffa48aa35a7bda4dc628cb4bcf54e12892232bb6852cbaf7250e5a9887864f987e36ef8e275c6f2262ca60ba4c167ad99de45b6c2d

data/CHANGELOG

@@ -1,4 +1,23 @@
-0.2.0 (2018-07-213)
+------------------
+0.2.3
+------------------
+
+------------------
+0.2.2  (2018-07-13)
+------------------
+
+* Fix path to git-release (assume it is properly installed)
+* Fix release date handling in CHANGELOG
+
+------------------
+0.2.1 (2018-07-13)
+------------------
+
+* Add dependency to github-release
+* Add release script
+
+------------------
+0.2.0 (2018-07-13)
 ------------------
 
 * Initial release.

data/README.md

@@ -4,7 +4,7 @@ The idea is to script most of the maintenance tasks so the maintainer can focus
 
 - Note: the workflow is highly inspired to the git-topic-branches (https://github.com/nmorey/git-topic-branches)
   and both can be used at the same time
-- Note2: Releasing on github is done through the git-release (https://github.com/mpalmer/github-release)
+- Note2: Releasing on github is done through github-release gem (https://github.com/mpalmer/github-release)
 
 # Command summary
 

data/lib/branch.rb

@@ -404,6 +404,7 @@ module GitMaintain
 
         def steal_one(opts, commit)
 		    subj=@repo.runGit("log -1 --format=\"%s\" #{commit}")
+            subj.gsub!(/"/, '\"')
 		    msg=''
 
 		    # Let's grab the mainline commit id, this is useful if the version tag

data/lib/repo.rb

@@ -2,7 +2,7 @@ module GitMaintain
     class Repo
         VALID_REPO = "github"
         STABLE_REPO = "stable"
-        SUBMIT_BINARY="/usr/bin/git-release.ruby2.5"
+        SUBMIT_BINARY="git-release"
 
         ACTION_LIST = [
             :list_branches,

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: git-maintain
 version: !ruby/object:Gem::Version
-  version: 0.2.0
+  version: 0.2.2.pre.1.gc26b949
 platform: ruby
 authors:
 - Nicolas Morey-Chaisemartin
@@ -9,7 +9,21 @@ autorequire:
 bindir: bin
 cert_chain: []
 date: 2018-07-13 00:00:00.000000000 Z
-dependencies: []
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: github-release
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :runtime
+  prerelease: false
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - ">="
+      - !ruby/object:Gem::Version
+        version: '0'
 description: |-
   Be lazy and let git-maintain do all the heavy lifting for maintaining stable branches.
   Leaves you only with the essential: reviewing the selected patches and decide where they should go.
@@ -44,9 +58,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
-  - - ">="
+  - - ">"
     - !ruby/object:Gem::Version
-      version: '0'
+      version: 1.3.1
 requirements: []
 rubyforge_project: 
 rubygems_version: 2.7.7