git-maintain 0.2.0.pre.6.g6c73de5 → 0.2.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (5) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG +1 -15
  3. data/README.md +1 -1
  4. data/lib/repo.rb +1 -1
  5. metadata +4 -18
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 7e420d50fcec0bf274a03d0da34b2f922d43d4ece5ff0f3906658ffc0dee74ef
4
- data.tar.gz: b781aba66879e2e92354a663d1918019152ef257777621b7d7285832c832b9a0
3
+ metadata.gz: 216d826fe15a57ca1d457a39bb20368b64eca217ac4f7a5b2119af8b7d775336
4
+ data.tar.gz: 9ad2d84895fe7116dcf6b96fcca0b1b217692a2376affa2e41306ac38691902c
5
5
  SHA512:
6
- metadata.gz: ae602b4ddd38c22a1e244466b2f836a3da0bc631ef82ba1619caa044246d9fa2fd162188d37ba6055b23d575e1da9ccc41fcfafdcdae1dc4079f6c09d6837a02
7
- data.tar.gz: b5ffb633d6c25a6a7c66e91c75def3f512cd77e069651a0beabcf374a168b39f0c4be9dc249c4b7aec490345feb796532d7834958b52758c5205ae47fe4397c4
6
+ metadata.gz: 3395184297ab04b2f13644bd3cba9bdbb45841bf0d96742a8726f3ff58e9b991895f7f9a029445a5bdabae481286c2e89462cc238cd525405ef1da0a35fb3e9f
7
+ data.tar.gz: 5b7f168f776ff74203c1e5e609d365e62151bb19c21514faf17b5e80adaed38f4c5349adaf08c8be4feda4b5703578a7126ee71467c2beafb43b01d04fe0be64
data/CHANGELOG CHANGED
@@ -1,18 +1,4 @@
1
- ------------------
2
- 0.2.2
3
- ------------------
4
-
5
- * Fix path to git-release (assume it is properly installed)
6
-
7
- ------------------
8
- 0.2.1 (2018-07-13)
9
- ------------------
10
-
11
- * Add dependency to github-release
12
- * Add release script
13
-
14
- ------------------
15
- 0.2.0 (2018-07-13)
1
+ 0.2.0 (2018-07-213)
16
2
  ------------------
17
3
 
18
4
  * Initial release.
data/README.md CHANGED
@@ -4,7 +4,7 @@ The idea is to script most of the maintenance tasks so the maintainer can focus
4
4
 
5
5
  - Note: the workflow is highly inspired to the git-topic-branches (https://github.com/nmorey/git-topic-branches)
6
6
  and both can be used at the same time
7
- - Note2: Releasing on github is done through github-release gem (https://github.com/mpalmer/github-release)
7
+ - Note2: Releasing on github is done through the git-release (https://github.com/mpalmer/github-release)
8
8
 
9
9
  # Command summary
10
10
 
data/lib/repo.rb CHANGED
@@ -2,7 +2,7 @@ module GitMaintain
2
2
  class Repo
3
3
  VALID_REPO = "github"
4
4
  STABLE_REPO = "stable"
5
- SUBMIT_BINARY="git-release"
5
+ SUBMIT_BINARY="/usr/bin/git-release.ruby2.5"
6
6
 
7
7
  ACTION_LIST = [
8
8
  :list_branches,
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: git-maintain
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.2.0.pre.6.g6c73de5
4
+ version: 0.2.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Nicolas Morey-Chaisemartin
@@ -9,21 +9,7 @@ autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
11
  date: 2018-07-13 00:00:00.000000000 Z
12
- dependencies:
13
- - !ruby/object:Gem::Dependency
14
- name: github-release
15
- requirement: !ruby/object:Gem::Requirement
16
- requirements:
17
- - - ">="
18
- - !ruby/object:Gem::Version
19
- version: '0'
20
- type: :runtime
21
- prerelease: false
22
- version_requirements: !ruby/object:Gem::Requirement
23
- requirements:
24
- - - ">="
25
- - !ruby/object:Gem::Version
26
- version: '0'
12
+ dependencies: []
27
13
  description: |-
28
14
  Be lazy and let git-maintain do all the heavy lifting for maintaining stable branches.
29
15
  Leaves you only with the essential: reviewing the selected patches and decide where they should go.
@@ -58,9 +44,9 @@ required_ruby_version: !ruby/object:Gem::Requirement
58
44
  version: '0'
59
45
  required_rubygems_version: !ruby/object:Gem::Requirement
60
46
  requirements:
61
- - - ">"
47
+ - - ">="
62
48
  - !ruby/object:Gem::Version
63
- version: 1.3.1
49
+ version: '0'
64
50
  requirements: []
65
51
  rubyforge_project:
66
52
  rubygems_version: 2.7.7