redmine_stagecoach 0.5.0 → 0.5.1

Sign up to get free protection for your applications and to get access to all the features.
data/README.rdoc CHANGED
@@ -1,7 +1,7 @@
1
1
  = Stagecoach
2
2
  stagecoach works in two stages, init and deploy. The init stage creates a branch based on a redmine/planio issue, and the deploy stage pushes, merges and (yes!) deploys it.
3
3
 
4
- *You should always run stagecoach from the root directory of your repo*
4
+ <b>You should always run stagecoach from the root directory of your repo</b>
5
5
  Otherwise it may (will) break.
6
6
 
7
7
  The first time you run stagecoach it will ask you for some information, namely your redmine/planio repo URL and your API key for this repo.
@@ -10,9 +10,8 @@ It will also install a custom commit-msg git hook (if you ask it to) - for more
10
10
  All stagecoach config is saved in /path/to/your/repo/.stagecoach which is created at initial setup and added to your global .gitignore. This is a yaml file with fairly obvious syntax
11
11
  so if you need to remove a branch or edit the issue number that a branch points to, it is possible (although not necessarily recommended) to edit it.
12
12
 
13
- Init Stage
14
- ==========
15
- stagecoach -p[lanio] 4115 (OR) -g[ithub] 525 -b[ranch] my_new_branch
13
+ == Init Stage
14
+ stagecoach -p[lanio] 4115 (OR) -g[ithub] 525 -b[ranch] my_new_branch
16
15
 
17
16
  You can also just run stagecoach without any flags and it will allow you to enter this stuff manually.
18
17
 
@@ -24,27 +23,24 @@ in your browser and do this manually. It also sets up a git issue for you to re
24
23
 
25
24
  If you are working from a github issue, we can all get on with our lives.
26
25
 
27
- Coding Stage
28
- ============
26
+ == Coding Stage
29
27
  Future versions of stagecoach may do the coding for you, but at the moment you have to do this part manually.
30
28
  Just code and commit, code and commit until your feature or fix is ready.
31
29
 
32
- Commit-msg githook
33
- ------------------
30
+ <b>Commit-msg githook</b>
34
31
  If you opt to install the commit-msg githook during initial setup (stagecoach -s) then your commit messages will be automatically referenced to the github issue of the branch you are in
35
32
  (this only applies to branches created or registered in Stagecoach).
36
33
 
37
- - to reference a different issue from a commit, simply refer to it as normal with #xxx in the commit message. The git-hook will leave your message alone.
38
- - to make no reference at all, you can use the #noref tag in the commit message. The git-hook
39
- - to close an issue with a commit, use the #closes tag.
34
+ * to reference a different issue from a commit, simply refer to it as normal with `#xxx` in the commit message. The git-hook will leave your message alone.
35
+ * to make no reference at all, you can use the `#noref` tag in the commit message.
36
+ * to close an issue with a commit, use the `#closes` tag.
40
37
 
41
38
  For more information, see
42
- - the githook itself at /path/to/your/repo/.git/hooks/commit-msg
43
- - http://book.git-scm.com/5_git_hooks.html
39
+ * the githook itself at `/path/to/your/repo/.git/hooks/commit-msg`
40
+ * http://book.git-scm.com/5_git_hooks.html
44
41
 
45
- Deploy Stage
46
- ============
47
- stagecoach -d[eploy]
42
+ == Deploy Stage
43
+ stagecoach -d[eploy]
48
44
 
49
45
  This automates the entire deploy workflow for you as follows:
50
46
 
@@ -56,14 +52,14 @@ This automates the entire deploy workflow for you as follows:
56
52
  cap staging deploy
57
53
  set redmine/planio ticket to 'feedback' status (if applicable)
58
54
 
59
- Sample usage:
55
+ <b> Sample usage: </b>
60
56
  stagecoach -p 4115 -b new_branch_name
61
57
  [code, commit until feature or fix is complete]
62
58
  stagecoach -d
63
59
 
64
- Flags
65
- --branch, -b: Enter your new branch name here, eg. stagecoach -b new_branch (optional)
66
- --planio, -p: Enter your planio issue number here, eg. stagecoach -p 1234 (optional)
67
- --github, -g: Enter your github issue number here, eg. stagecoach -g 1234 (optional)
68
- --deploy, -d: Use this option to skip straight to push & deploy if you have already pulled from master and created your new branch
69
- --setup, -s: Use this the first time you run stagecoach to save your redmine repository/api key and install the commit-msg githook if desired
60
+ <b> Flags </b>
61
+ --branch, -b: Enter your new branch name here, eg. stagecoach -b new_branch (optional)
62
+ --planio, -p: Enter your planio issue number here, eg. stagecoach -p 1234 (optional)
63
+ --github, -g: Enter your github issue number here, eg. stagecoach -g 1234 (optional)
64
+ --deploy, -d: Use this option to skip straight to push & deploy if you have already pulled from master and created your new branch
65
+ --setup, -s: Use this the first time you run stagecoach to save your redmine repository/api key and install the commit-msg githook if desired
data/VERSION CHANGED
@@ -1 +1 @@
1
- 0.5.0
1
+ 0.5.1
@@ -24,6 +24,7 @@
24
24
  # cd your_project
25
25
  # ~/.githooks/commit-msg .git/hooks
26
26
 
27
+ require 'rubygems'
27
28
  require 'yaml'
28
29
 
29
30
  # Custom method to check for installed redmine_stagecoach gem
@@ -5,11 +5,11 @@
5
5
 
6
6
  Gem::Specification.new do |s|
7
7
  s.name = "redmine_stagecoach"
8
- s.version = "0.5.0"
8
+ s.version = "0.5.1"
9
9
 
10
10
  s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
11
11
  s.authors = ["Oli Barnett"]
12
- s.date = "2012-01-24"
12
+ s.date = "2012-01-26"
13
13
  s.description = "Git/capistrano workflow automation script with Redmine & Github issue integration"
14
14
  s.email = "o.barnett@digitaleseiten.de"
15
15
  s.executables = ["stagecoach"]
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: redmine_stagecoach
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.5.0
4
+ version: 0.5.1
5
5
  prerelease:
6
6
  platform: ruby
7
7
  authors:
@@ -9,11 +9,11 @@ authors:
9
9
  autorequire:
10
10
  bindir: bin
11
11
  cert_chain: []
12
- date: 2012-01-24 00:00:00.000000000Z
12
+ date: 2012-01-26 00:00:00.000000000Z
13
13
  dependencies:
14
14
  - !ruby/object:Gem::Dependency
15
15
  name: ghi
16
- requirement: &70166234091840 !ruby/object:Gem::Requirement
16
+ requirement: &70340781782300 !ruby/object:Gem::Requirement
17
17
  none: false
18
18
  requirements:
19
19
  - - ! '>='
@@ -21,10 +21,10 @@ dependencies:
21
21
  version: '0'
22
22
  type: :runtime
23
23
  prerelease: false
24
- version_requirements: *70166234091840
24
+ version_requirements: *70340781782300
25
25
  - !ruby/object:Gem::Dependency
26
26
  name: trollop
27
- requirement: &70166234091360 !ruby/object:Gem::Requirement
27
+ requirement: &70340781781820 !ruby/object:Gem::Requirement
28
28
  none: false
29
29
  requirements:
30
30
  - - ! '>='
@@ -32,10 +32,10 @@ dependencies:
32
32
  version: '0'
33
33
  type: :runtime
34
34
  prerelease: false
35
- version_requirements: *70166234091360
35
+ version_requirements: *70340781781820
36
36
  - !ruby/object:Gem::Dependency
37
37
  name: capistrano
38
- requirement: &70166234090880 !ruby/object:Gem::Requirement
38
+ requirement: &70340781781340 !ruby/object:Gem::Requirement
39
39
  none: false
40
40
  requirements:
41
41
  - - ! '>='
@@ -43,10 +43,10 @@ dependencies:
43
43
  version: '0'
44
44
  type: :runtime
45
45
  prerelease: false
46
- version_requirements: *70166234090880
46
+ version_requirements: *70340781781340
47
47
  - !ruby/object:Gem::Dependency
48
48
  name: shoulda
49
- requirement: &70166234090400 !ruby/object:Gem::Requirement
49
+ requirement: &70340781780860 !ruby/object:Gem::Requirement
50
50
  none: false
51
51
  requirements:
52
52
  - - ! '>='
@@ -54,10 +54,10 @@ dependencies:
54
54
  version: '0'
55
55
  type: :development
56
56
  prerelease: false
57
- version_requirements: *70166234090400
57
+ version_requirements: *70340781780860
58
58
  - !ruby/object:Gem::Dependency
59
59
  name: bundler
60
- requirement: &70166234089920 !ruby/object:Gem::Requirement
60
+ requirement: &70340781780380 !ruby/object:Gem::Requirement
61
61
  none: false
62
62
  requirements:
63
63
  - - ~>
@@ -65,10 +65,10 @@ dependencies:
65
65
  version: 1.0.0
66
66
  type: :development
67
67
  prerelease: false
68
- version_requirements: *70166234089920
68
+ version_requirements: *70340781780380
69
69
  - !ruby/object:Gem::Dependency
70
70
  name: jeweler
71
- requirement: &70166234089440 !ruby/object:Gem::Requirement
71
+ requirement: &70340781779900 !ruby/object:Gem::Requirement
72
72
  none: false
73
73
  requirements:
74
74
  - - ~>
@@ -76,10 +76,10 @@ dependencies:
76
76
  version: 1.6.4
77
77
  type: :development
78
78
  prerelease: false
79
- version_requirements: *70166234089440
79
+ version_requirements: *70340781779900
80
80
  - !ruby/object:Gem::Dependency
81
81
  name: rcov
82
- requirement: &70166234088960 !ruby/object:Gem::Requirement
82
+ requirement: &70340781779420 !ruby/object:Gem::Requirement
83
83
  none: false
84
84
  requirements:
85
85
  - - ! '>='
@@ -87,7 +87,7 @@ dependencies:
87
87
  version: '0'
88
88
  type: :development
89
89
  prerelease: false
90
- version_requirements: *70166234088960
90
+ version_requirements: *70340781779420
91
91
  description: Git/capistrano workflow automation script with Redmine & Github issue
92
92
  integration
93
93
  email: o.barnett@digitaleseiten.de
@@ -133,7 +133,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
133
133
  version: '0'
134
134
  segments:
135
135
  - 0
136
- hash: 2500404004806684746
136
+ hash: -4338871713732434761
137
137
  required_rubygems_version: !ruby/object:Gem::Requirement
138
138
  none: false
139
139
  requirements: