big_keeper 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: 9b396b98833d0bbe44d9345410e70963209fcb7b
+  data.tar.gz: 956e4effcef9a81e3c3e9eb062882f2b12ea0a5f
+SHA512:
+  metadata.gz: 0ed9db1e01734561b65d052fb2fbfab216e2c26753ef3d37374ebf0995da3ffe3bc6b6ed2e2642f94bea25ac0217fdae0d7d873429eae6993af58f0e2e85d536
+  data.tar.gz: 468006350087e7a75dbf23dbb1edd94db6beae239d4a8e62cb031afd9011ec0b2e5fa17b02771aa4018e1e3244b1867cafd24f1f2486b469834f675f94f32418

data/.gitignore

@@ -0,0 +1,50 @@
+*.gem
+*.rbc
+/.config
+/coverage/
+/InstalledFiles
+/pkg/
+/spec/reports/
+/spec/examples.txt
+/test/tmp/
+/test/version_tmp/
+/tmp/
+
+# Used by dotenv library to load environment variables.
+# .env
+
+## Specific to RubyMotion:
+.dat*
+.repl_history
+build/
+*.bridgesupport
+build-iPhoneOS/
+build-iPhoneSimulator/
+
+## Specific to RubyMotion (use of CocoaPods):
+#
+# We recommend against adding the Pods directory to your .gitignore. However
+# you should judge for yourself, the pros and cons are mentioned at:
+# https://guides.cocoapods.org/using/using-cocoapods.html#should-i-check-the-pods-directory-into-source-control
+#
+# vendor/Pods/
+
+## Documentation cache and generated files:
+/.yardoc/
+/_yardoc/
+/doc/
+/rdoc/
+
+## Environment normalization:
+/.bundle/
+/vendor/bundle
+/lib/bundler/man/
+
+# for a library or gem, you might want to ignore these files since the code is
+# intended to run in multiple environments; otherwise, check them in:
+# Gemfile.lock
+# .ruby-version
+# .ruby-gemset
+
+# unless supporting rvm < 1.11.0 or doing something fancy, ignore this:
+.rvmrc

data/Gemfile

@@ -0,0 +1,6 @@
+source "https://ruby.taobao.org"
+
+git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
+
+# Specify your gem's dependencies in big_keeper.gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,106 @@
+PATH
+  remote: .
+  specs:
+    big_keeper (0.1.0)
+
+GEM
+  remote: https://ruby.taobao.org/
+  specs:
+    CFPropertyList (2.3.3)
+    activesupport (4.2.7.1)
+      i18n (~> 0.7)
+      json (~> 1.7, >= 1.7.7)
+      minitest (~> 5.1)
+      thread_safe (~> 0.3, >= 0.3.4)
+      tzinfo (~> 1.1)
+    ast (2.3.0)
+    big_stash (0.2.0)
+    claide (1.0.1)
+    cocoapods (1.2.1)
+      activesupport (>= 4.0.2, < 5)
+      claide (>= 1.0.1, < 2.0)
+      cocoapods-core (= 1.2.1)
+      cocoapods-deintegrate (>= 1.0.1, < 2.0)
+      cocoapods-downloader (>= 1.1.3, < 2.0)
+      cocoapods-plugins (>= 1.0.0, < 2.0)
+      cocoapods-search (>= 1.0.0, < 2.0)
+      cocoapods-stats (>= 1.0.0, < 2.0)
+      cocoapods-trunk (>= 1.2.0, < 2.0)
+      cocoapods-try (>= 1.1.0, < 2.0)
+      colored2 (~> 3.1)
+      escape (~> 0.0.4)
+      fourflusher (~> 2.0.1)
+      gh_inspector (~> 1.0)
+      molinillo (~> 0.5.7)
+      nap (~> 1.0)
+      ruby-macho (~> 1.1)
+      xcodeproj (>= 1.4.4, < 2.0)
+    cocoapods-core (1.2.1)
+      activesupport (>= 4.0.2, < 5)
+      fuzzy_match (~> 2.0.4)
+      nap (~> 1.0)
+    cocoapods-deintegrate (1.0.1)
+    cocoapods-downloader (1.1.3)
+    cocoapods-plugins (1.0.0)
+      nap
+    cocoapods-search (1.0.0)
+    cocoapods-stats (1.0.0)
+    cocoapods-trunk (1.2.0)
+      nap (>= 0.8, < 2.0)
+      netrc (= 0.7.8)
+    cocoapods-try (1.1.0)
+    colored2 (3.1.2)
+    escape (0.0.4)
+    fourflusher (2.0.1)
+    fuzzy_match (2.0.4)
+    gh_inspector (1.0.2)
+    gli (2.16.1)
+    i18n (0.7.0)
+    json (1.8.3)
+    minitest (5.8.3)
+    molinillo (0.5.7)
+    nanaimo (0.2.3)
+    nap (1.1.0)
+    netrc (0.7.8)
+    parallel (1.12.0)
+    parser (2.4.0.0)
+      ast (~> 2.2)
+    plist (3.3.0)
+    powerpack (0.1.1)
+    rainbow (2.2.2)
+      rake
+    rake (10.5.0)
+    rubocop (0.50.0)
+      parallel (~> 1.10)
+      parser (>= 2.3.3.1, < 3.0)
+      powerpack (~> 0.1)
+      rainbow (>= 2.2.2, < 3.0)
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (~> 1.0, >= 1.0.1)
+    ruby-macho (1.1.0)
+    ruby-progressbar (1.9.0)
+    thread_safe (0.3.5)
+    tzinfo (1.2.2)
+      thread_safe (~> 0.1)
+    unicode-display_width (1.3.0)
+    xcodeproj (1.4.4)
+      CFPropertyList (~> 2.3.3)
+      claide (>= 1.0.1, < 2.0)
+      colored2 (~> 3.1)
+      nanaimo (~> 0.2.3)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  big_keeper!
+  big_stash (~> 0.1)
+  bundler (~> 1.15)
+  cocoapods
+  gli (~> 2.16)
+  plist
+  rake (~> 10.0)
+  rubocop (~> 0.50.0)
+
+BUNDLED WITH
+   1.15.4

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2017 mmoaay
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,41 @@
+[中文](docs/zh-CN/README.md)
+
+---
+
+# big-keeper - All in home project
+
+big-keeper is an efficiency improvement for iOS modular development, iOSer using this tool can make modular development easier.
+
+## Installation
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem 'big_keeper'
+```
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install big_keeper
+
+## Usage
+
+Run `big-keeper` to learn how to use big-keeper.
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/BigKeeper/big-keeper.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).

data/Rakefile

@@ -0,0 +1,2 @@
+require "bundler/gem_tasks"
+task :default => :spec

data/big_keeper.gemspec

@@ -0,0 +1,40 @@
+# coding: utf-8
+lib = File.expand_path("../lib", __FILE__)
+$LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
+require "big_keeper/version"
+
+Gem::Specification.new do |spec|
+  spec.name          = "big_keeper"
+  spec.version       = BigKeeper::VERSION
+  spec.authors       = ["mmoaay"]
+  spec.email         = ["mmoaay@sina.com"]
+
+  spec.summary       = %q{Efficiency improvement for iOS modular development.}
+  spec.description   = %q{Efficiency improvement for iOS modular development, iOSer using this tool can make modular development easier.}
+  spec.homepage      = "https://github.com/BigKeeper/big-keeper"
+  spec.license       = "MIT"
+
+  # Prevent pushing this gem to RubyGems.org. To allow pushes either set the 'allowed_push_host'
+  # to allow pushing to a single host or delete this section to allow pushing to any host.
+  if spec.respond_to?(:metadata)
+    spec.metadata["allowed_push_host"] = "https://rubygems.org"
+  else
+    raise "RubyGems 2.0 or newer is required to protect against " \
+      "public gem pushes."
+  end
+
+  spec.files         = `git ls-files -z`.split("\x0").reject do |f|
+    f.match(%r{^(test|spec|features)/})
+  end
+  spec.bindir        = "bin"
+  spec.executables   = spec.files.grep(%r{^bin/}) { |f| File.basename(f) }
+  spec.require_paths = ["lib"]
+
+  spec.add_development_dependency "bundler", "~> 1.15"
+  spec.add_development_dependency "rake", "~> 10.0"
+  spec.add_development_dependency "gli", "~> 2.16"
+  spec.add_development_dependency "big_stash", "~> 0.1"
+  spec.add_development_dependency "cocoapods"
+  spec.add_development_dependency "plist"
+  spec.add_development_dependency "rubocop", "~> 0.50.0"
+end

data/bin/big-keeper

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "big_keeper"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/docs/zh-CN/BIGKEEPER_FILE.md

@@ -0,0 +1,62 @@
+# Bigkeeper 文件
+
+首先，我们在主项目 Podfile 所在的目录加入 `Bigkeeper` 文件。
+
+## 配置版本
+
+```
+version '2.8.8'
+```
+
+版本号的用途有：
+
+- feature 和 hotfix 流程里面做为分支名前缀的一部分，方便后期通过版本号匹配分支；
+- release 流程里面做为发布版本号，影响范围包括业务模块和主项目。
+
+## 配置主项目
+
+```
+home 'BigKeeperMain', :git => 'git@github.com:BigKeeper/BigKeeperMain.git', :pulls => 'https://github.com/BigKeeper/BigKeeperMain/pulls'
+```
+
+这个配置包含三个部分：
+
+- 主项目的名字；
+- 主项目的 git 远程仓库地址；
+- 主项目的 pull request / merge request 页面地址，完成某个 feature / hotfix 时，会自动打开这个页面，让开发者提交 pull request / merge request。
+
+## 配置业务模块
+
+```
+modules do
+  pod 'BigKeeperModular', :git => 'git@github.com:BigKeeper/BigKeeperModular.git', :pulls => 'https://github.com/BigKeeper/BigKeeperModular/pulls'
+end
+```
+
+这个配置包含可以配置多个业务模块，建议是把当前所有非第三方库都加入到这个配置里面：
+
+- 业务模块在 Podfile 中的名字；
+- 业务模块的 git 远程仓库地址；
+- 业务模块的 pull request / merge request 页面地址，完成某个 feature / hotfix 时，会自动打开这个页面，让开发者提交 pull request / merge request。
+
+## 配置用户自定义信息
+
+```
+user 'perry' do
+  pod 'BigKeeperModular', :path => '../BigKeeperModular'
+end
+```
+
+如果用户需要配置一些自定义信息，比如业务模块在本地的路径，就可以增加一个这样的配置。
+
+这个配置同样支持对指定的用户名（上述配置用户名为 perry）配置多个业务模块，目前支持的是：
+
+- 配置业务模块的本地路径，通过这个路径，我们就可以在主工程直接对业务模块做一些 CocoaPods 和 git 相关的操作。
+
+> 注：
+>
+> 1. 默认用户名是 git global config 的 user.name；
+>
+> 2. 默认我们会把本地路径配置成 `../{业务模块在 Podfile 中的名字}` 的形式，因为大部分情况下，我们会把项目都放在同级目录下，这也是我们推荐的；
+>
+> 3. 另外，在使用 big-keeper 相关功能时，如果某些业务模块并没有 clone 到本地，big-keeper 会根据之前配置的业务模块远程 git 地址 clone 业务模块仓库到**主项目同级目录下**。

data/docs/zh-CN/FEATURE.md

@@ -0,0 +1,88 @@
+# feature - 功能开发流程
+
+直接在命令行执行 `big-keeper feature --help` 可以查看其提供的所有功能：
+
+```
+NAME
+    feature - Feature operations
+
+SYNOPSIS
+    big-keeper [global options] feature [command options] finish
+    big-keeper [global options] feature [command options] list
+    big-keeper [global options] feature [command options] pull
+    big-keeper [global options] feature [command options] push
+    big-keeper [global options] feature [command options] start
+    big-keeper [global options] feature [command options] switch
+    big-keeper [global options] feature [command options] update
+
+COMMAND OPTIONS
+    -u, --user=arg - (default: mmoaay)
+
+COMMANDS
+    finish - Finish current feature
+    list   - List all the features
+    pull   - Pull remote changes for current feature
+    push   - Push local changes to remote for current feature
+    start  - Start a new feature with name for given modules and main project
+    switch - Switch to the feature with name
+    update - Update moduels for the feature with name
+```
+
+全局参数如下：
+
+- -u, --user：用户名，默认是 git global config 的 user.name，会显示在命令提示信息中，比如上述提示信息中的默认用户名是 mmoaay
+
+功能列表如下：
+
+- start：
+  开始一个新的 feature，输入参数依次为：
+  - feature 的名字;
+  - 开发该 feature 需要改动的业务模块名。可以多个，用空格隔开；如果不指定，取 **Bigkeeper 文件中所有的业务模块名**。
+- finish：结束当前 feature；
+- switch：切换到一个已经存在的 feature，输入参数为 feature 名；
+- update：
+  更新一个 feature 需要改动的业务模块，输入参数依次为：
+  - feature 的名字;
+  - 开发该 feature 需要改动的业务模块名。可以多个，用空格隔开；如果不指定，取 **Bigkeeper 文件中所有的业务模块名**。
+- pull：拉取当前 feature 主项目和业务模块的远程 git 仓库更新；
+- push：提交并推送当前 feature 主项目和业务模块的本地变更到远程 git 仓库，输入参数为提交信息；
+- list：显示当前的 feature 列表。
+
+## feature 的工作区
+
+![](../../resources/readme/big-keeper-readme.001.png)
+
+feature 的工作区主要由两部分组成：
+
+- 主项目；
+- 相关业务模块，我们把 Podfile 中引用方式为 `:path => {业务模块本地路径}` 的模块做为相关业务模块。
+
+主项目和每个相关业务模块又有各自的工作区，由三个部分组成：
+
+- 当前代码区改动；
+- stash 缓存区，当用户需要切换新的 feature 时，对于用户来不及提交的改动，我们会缓存到各个项目的 stash 中，（PS：所以代码突然不见了不要担心，都在 git 的 stash 里面），而当用户切换回某个 feature 时，我们会把和该 feature 分支同名的 stash 恢复回来，从而使用户可以继续开发之前未完成的部分，因为需要通过 feature 的分支名来匹配 stash，而 git stash 又没有提供给 stash 命名的功能，所以我们实现了 [big-stash](https://github.com/BigKeeper/big-stash) 来完成这个功能；
+- git。
+
+## feature start 流程
+
+![](../../resources/readme/big-keeper-readme.002.png)
+
+## feature finish 流程
+
+![](../../resources/readme/big-keeper-readme.003.png)
+
+## feature switch 流程
+
+![](../../resources/readme/big-keeper-readme.004.png)
+
+## feature update 流程
+
+![](../../resources/readme/big-keeper-readme.005.png)
+
+## feature pull 流程
+
+![](../../resources/readme/big-keeper-readme.006.png)
+
+## feature push 流程
+
+![](../../resources/readme/big-keeper-readme.007.png)

data/docs/zh-CN/README.md

@@ -0,0 +1,76 @@
+[English](../../README.md)
+
+---
+
+# big-keeper - 我好像做了一个假的模块化项目
+
+big-keeper 是一个**iOS模块化项目过渡阶段**的效率提升工具，使用这个工具后，开发者**在主项目内**就可以完成**包括其他业务模块在内**所有代码的编写和管理。
+
+> 注：目前只支持依赖 CocoaPods 管理的模块化工程。
+
+我们仿照 CocoaPods 的做法，开发团队只需要在主项目中加入一个 Bigkeeper 文件，然后利用我们提供的 `big-keeper` 工具，即可更便捷的实现**代码分支**和**业务模块**的管理；另外，通过我们提供的工具，也能帮助开发者养成更规范的日常开发习惯，减轻项目管理者的负担。
+
+## 应用场景
+
+在模块化项目的过渡阶段，我们往往会碰到业务拆分不是那么彻底的情况（PS：比如主项目中仍然存在业务相关代码），这样就会导致一系列问题：
+
+- 开发者开发一个 feature 时需要维护多个项目的分支，同时还要频繁修改主项目的 `Podfile`;
+- 项目管理者需要花很大精力去和团队成员同步项目管理规范流程，尤其对于新人，挑战很大；
+- 开发过程中如果碰到突发情况需要开新分支处理问题时对当前工作区的保存操作会很繁琐（PS：因为涉及到多个项目）；
+- 日常开发过程中类似 commit、pull、push 等操作比较繁琐（PS：因为涉及到多个项目）。
+
+big-keeper 的出现就是为了解决这些问题。
+
+> 注：也有很多人认为直接做一个完整的组件化项目更合理，而不需要采用这样曲折的方案，但是很多时候我们并没有这么多的精力直接去做这些事情，big-keeper 存在的价值也是为了帮助开发团队在**iOS模块化项目过渡阶段**能更轻松的往前走。
+
+## 安装
+
+- 当作 Ruby Gem 使用：
+  在项目的 Gemfile 中加入下面这行：
+
+  ```ruby
+  gem 'big_keeper'
+  ```
+
+  然后执行：
+
+    $ bundle
+
+- 直接安装：
+
+    $ gem install big_keeper
+
+## 使用方法
+
+- [Bigkeeper 文件配置](BIGKEEPER_FILE.md)
+- `big-keeper` 工具使用：
+
+  直接在命令行执行 `big-keeper` 可以查看其提供的所有功能：
+
+  ```
+  NAME
+      big-keeper - Efficiency improvement for iOS modular development, iOSer using this tool can make modular development easier.
+
+  SYNOPSIS
+      big-keeper [global options] command [command options] [arguments...]
+
+  GLOBAL OPTIONS
+      --help         - Show this message
+      -p, --path=arg - (default: ./)
+      -v, --ver=arg  - (default: Version in Bigkeeper file)
+
+  COMMANDS
+      feature - Feature operations
+      help    - Shows a list of commands or help for one command
+      release - Release operations
+  ```
+
+  全局参数如下：
+
+  - -p, --path：主项目所在的目录，默认是执行 big-keeper 命令的当前目录；
+  - -v, --ver：版本号，如果没有指定的话，会以主项目 [Bigkeeper 文件](BIGKEEPER_FILE.md)中指定的版本为准。
+
+  功能列表如下：
+
+  - [feature](FEATURE.md)：功能开发流程；
+  - [release](RELEASE.md)：版本发布流程。

data/lib/big_keeper/command/feature_finish.rb

@@ -0,0 +1,47 @@
+#!/usr/bin/ruby
+
+require 'big_keeper/util/podfile_operator'
+require 'big_keeper/util/bigkeeper_parser'
+
+require 'big_keeper/model/podfile_type'
+
+module BigKeeper
+
+  def self.feature_finish(path, user)
+    begin
+      # Parse Bigkeeper file
+      BigkeeperParser.parse("#{path}/Bigkeeper")
+
+      modules = PodfileOperator.new.modules_with_type("#{path}/Podfile",
+                                BigkeeperParser.module_names, ModuleType::PATH)
+
+      branch_name = GitOperator.new.current_branch(path)
+      raise "Not a feature branch, exit." unless branch_name.include? 'feature'
+
+      # Rebase modules and modify podfile as git
+      modules.each do |module_name|
+        ModuleService.new.finish(path, user, module_name)
+      end
+
+      BigkeeperParser.module_names.each do |module_name|
+        module_git = BigkeeperParser.module_git(module_name)
+        PodfileOperator.new.find_and_replace("#{path}/Podfile",
+                                             %Q('#{module_name}'),
+                                             ModuleType::GIT,
+                                             GitInfo.new(module_git, GitType::BRANCH, 'develop'))
+      end
+
+      # pod install
+      p `pod install --project-directory=#{path}`
+
+      # Push home changes to remote
+      GitOperator.new.commit(path, "finish #{GitflowType.name(GitflowType::FEATURE)} #{branch_name}")
+      GitOperator.new.push(path, branch_name)
+
+      GitService.new.verify_rebase(path, 'develop', 'Home')
+
+      `open #{BigkeeperParser.home_pulls()}`
+    ensure
+    end
+  end
+end

data/lib/big_keeper/command/feature_pull.rb

@@ -0,0 +1,23 @@
+module BigKeeper
+  def self.feature_pull(path, user)
+    begin
+      # Parse Bigkeeper file
+      BigkeeperParser.parse("#{path}/Bigkeeper")
+
+      branch_name = GitOperator.new.current_branch(path)
+      raise 'Not a feature branch, exit.' unless branch_name.include? 'feature'
+
+      modules = PodfileOperator.new.modules_with_type("#{path}/Podfile",
+                                                      BigkeeperParser.module_names, ModuleType::PATH)
+
+      modules.each do |module_name|
+        ModuleService.new.pull(path, user, module_name, branch_name)
+      end
+
+      p 'Start pulling home...'
+      GitOperator.new.pull(path, branch_name)
+      p 'Finish pulling home...'
+    ensure
+    end
+  end
+end

data/lib/big_keeper/command/feature_push.rb

@@ -0,0 +1,39 @@
+module BigKeeper
+
+  def self.feature_push(path, user, comment)
+    begin
+      # Parse Bigkeeper file
+      BigkeeperParser.parse("#{path}/Bigkeeper")
+
+      branch_name = GitOperator.new.current_branch(path)
+      raise "Not a feature branch, exit." unless branch_name.include? 'feature'
+
+      modules = PodfileOperator.new.modules_with_type("#{path}/Podfile",
+                                BigkeeperParser.module_names, ModuleType::PATH)
+
+      modules.each do |module_name|
+        module_full_path = BigkeeperParser.module_full_path(path, user, module_name)
+        module_branch_name = GitOperator.new.current_branch(module_full_path)
+
+        if GitOperator.new.has_changes(module_full_path)
+          p "Start pushing #{module_name}..."
+          GitOperator.new.commit(module_full_path, comment)
+          GitOperator.new.push(module_full_path, module_branch_name)
+          p "Finish pushing #{module_name}..."
+        else
+          p "Nothing to push for #{module_name}."
+        end
+      end
+
+      if GitOperator.new.has_changes(path)
+        p "Start pushing home..."
+        GitOperator.new.commit(path, comment)
+        GitOperator.new.push(path, branch_name)
+        p "Finish pushing home..."
+      else
+        p "Nothing to push for home."
+      end
+    ensure
+    end
+  end
+end