Project

gitcopier

0.0
No commit activity in last 3 years
No release in over 3 years
gitcopiertranvictor/gitcopierHomepageDocumentationSource CodeBug TrackerWiki
Sometime, you work for a Rails project but its front end is adopted from other repositories (such as separated repository from a front end developer who is not familiar with Rails) and you need to integrate front end changes to the project. You need to see what files were changed, copy them accordingly. This gem will help you do the job really fast.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
9,778
Stars
4
Forks
0
Watchers
1
 Releases
Current version
0.1.9
Total releases
4
First release
2015-10-21
Latest release
2015-10-22
 Issues
Open Issues
1
Closed Issues
0
Total Issues
1
Issue Closure Rate
0%
 Development
Primary Language
Ruby
Licenses
MIT
Average date of last 50 commits
2015-10-21
Reverse Dependencies
0

 Dependencies

Development

bundler
~> 1.7
rake
~> 10.0

Runtime

colorize
~> 0.7
 Project Readme

Gitcopier

Help developers to integrate between multiple repositories.

Gem Version Circle CI Code Climate

Installation

Add this line to your application's Gemfile:

gem 'gitcopier'

And then execute:

$ bundle

Or install it yourself as:

$ gem install gitcopier

Motivation

Imagine you are a Rails developer, your expertise is designing and developing backend logic so you have one or more front end developers to help you with design, javascript, stylesheet ... However, they are working in Nodejs environment which is pretty different to Rails environment thus they have different repository. In order to apply (integrate) changes from that repository, you might have to see what files were changed, copy them to appropriate places in your Rails repository. Doing so is really annoying. You should have a better way of doing it.

How Gitcopier work

Gitcopier helps you in intergrating those changes. Whenever you pull from front-end repository, Gitcopier will ask you to decide where to copy changed file (modified, added). It remembers your dicisions to automatically copy or not copy in the future without asking you. This way, if front-end developers commit a change to existing files, you just have to pull that repository and Gitcopier will do all copying works.

Usage

Tell Gitcopier your repositories

gitcopier --from <path_to_external_repo> --to <path_to_main_repo>

where:

  1. <path_to_external_repo>: is absolute path to the repository that you want Gitcopier to copy files from. This repo must be under git control.
  2. <path_to_main_repo>: is absolute path to the repository that you want Gitcopier to copy files to.

Note: gitcopier -h for help

gitcopier -h
Usage: gitcopier [options]
        --from [path]                Absolute path to your local repository that you want to copy from. This option must go with --to.
        --to [path]                  Absolute path to your local repository that you want to copy to. This option must go with --from.
    -v, --version
        --showall                    Show all integration information. This option ignore any other options.

Working with git merge

After you git pull in external repository, Gitcopier will prompt your decision where to copy the changed files. Gitcopier prompt

Contributing

  1. Fork it ( https://github.com/tranvictor/gitcopier/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request