ora-cli 0.2.4 → 0.2.5
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +26 -6
- data/lib/ora/cli/tasks/delete_feature_branch.rb +1 -1
- data/lib/ora/cli/version.rb +1 -1
- metadata +2 -2
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA1:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 507b9b589105165384636b713d9d0c3ce178d068
|
|
4
|
+
data.tar.gz: d9cf76f68eada80d4a11421fd87d95ba6352c9ca
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: bc80ddd7872fe0988a2ce5434a3df92a26835595002923b0c6ce5504b35b70ce1c9d3f97d7774b0f6246a15a8e8b7a54dae71e2fa0199ba5921ac2ba5e307f7f
|
|
7
|
+
data.tar.gz: 8532c9b269030f683cb80eb8a5461949a950e274be798f7e774c499048db593f3509a1b3f00e6094fff273bf64b090a8c42e3dc30cd9e07bca7d152fa906b1c2
|
data/README.md
CHANGED
|
@@ -21,17 +21,37 @@ A command line tool to automate development workflow in ORA
|
|
|
21
21
|
|
|
22
22
|
## Tasks
|
|
23
23
|
|
|
24
|
-
`new_feature_branch`:
|
|
24
|
+
`new_feature_branch`: Create a new branch from up-to-date develop branch
|
|
25
25
|
|
|
26
|
-
`push_feature_branch`:
|
|
26
|
+
`push_feature_branch`: Push current feature branch to remote ready for pull request
|
|
27
27
|
|
|
28
|
-
`
|
|
28
|
+
`delete_feature_branch`: Delete current feature branch
|
|
29
29
|
|
|
30
|
-
`
|
|
30
|
+
`push_to_staging`: Push current feature branch to staging
|
|
31
31
|
|
|
32
|
-
`
|
|
32
|
+
`push_to_uat`: Push current feature branch to uat
|
|
33
33
|
|
|
34
|
-
`
|
|
34
|
+
`push_to_master`: Push develop to master with a version tag with a message including all new pull requests from the previous tag
|
|
35
|
+
|
|
36
|
+
`switch_branch`: Switch branch without thinking about dirty files
|
|
37
|
+
|
|
38
|
+
## Custom develop branch
|
|
39
|
+
|
|
40
|
+
$ ora branch-name
|
|
41
|
+
|
|
42
|
+
You can parse a branch name to ora command to use it instead develop branch.
|
|
43
|
+
Useful when we need a second develop branch.
|
|
44
|
+
|
|
45
|
+
> push_to_master will still push from develop to master.
|
|
46
|
+
|
|
47
|
+
## Error handling
|
|
48
|
+
|
|
49
|
+
$ ora
|
|
50
|
+
|
|
51
|
+
When a task is failed, you can resolve the issue and run `ora` again to continue.
|
|
52
|
+
Ora-cli uses a file `~/.ora_continue` to save the state when a task is failed.
|
|
53
|
+
|
|
54
|
+
> To continue a failed task using custom develop branch, you need to type the custom branch name as an argument.
|
|
35
55
|
|
|
36
56
|
## Contributing
|
|
37
57
|
|
data/lib/ora/cli/version.rb
CHANGED
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: ora-cli
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.2.
|
|
4
|
+
version: 0.2.5
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- Ducksan Cho
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date: 2016-11-
|
|
11
|
+
date: 2016-11-28 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: bundler
|