Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/ekho/capistrano-git-submodule-strategy

Git submodule support for Capistrano 3
https://github.com/ekho/capistrano-git-submodule-strategy

Last synced: 3 months ago
JSON representation

Git submodule support for Capistrano 3

Host: GitHub
URL: https://github.com/ekho/capistrano-git-submodule-strategy
Owner: ekho
License: mit
Created: 2014-05-22T16:48:51.000Z (over 10 years ago)
Default Branch: master
Last Pushed: 2020-09-01T05:40:00.000Z (about 4 years ago)
Last Synced: 2024-05-11T19:44:59.839Z (6 months ago)
Language: Ruby
Size: 45.9 KB
Stars: 47
Watchers: 4
Forks: 20
Open Issues: 3
Metadata Files:
- Readme: README.md
- License: LICENSE

Awesome Lists containing this project

README

# capistrano-git-submodule-strategy [![Gem](https://img.shields.io/gem/v/capistrano-git-submodule-strategy.svg?maxAge=2592000)](https://rubygems.org/gems/capistrano-git-submodule-strategy) [![Gem](https://img.shields.io/gem/dt/capistrano-git-submodule-strategy.svg?maxAge=2592000)](https://rubygems.org/gems/capistrano-git-submodule-strategy)

Git submodule support for Capistrano 3.0-3.6.*

For Capistrano 3.7+ use new [capistrano-git-with-submodules](https://github.com/ekho/capistrano-git-with-submodules)

*Project is not in an active development and support.*

## Using

####Capfile
```ruby
require 'capistrano/git-submodule-strategy'
```

####Gemfile
```ruby
gem 'capistrano-git-submodule-strategy', '~> 0.1', :github => 'ekho/capistrano-git-submodule-strategy'
```

####deploy.rb
```ruby
set :scm, :git
set :git_strategy, Capistrano::Git::SubmoduleStrategy
```
Optionally you can keep git metadata (.git directory)
```ruby
set :git_keep_meta, true
```

## Contributing to capistrano-git-submodule-strategy

* Check out the latest master to make sure the feature hasn't been implemented or the bug hasn't been fixed yet.
* Check out the issue tracker to make sure someone already hasn't requested it and/or contributed it.
* Fork the project.
* Start a feature/bugfix branch.
* Commit and push until you are happy with your contribution.
* Make sure to add tests for it. This is important so I don't break it in a future version unintentionally.
* Please try not to mess with the Rakefile, version, or history. If you want to have your own version, or is otherwise necessary, that is fine, but please isolate to its own commit so I can cherry-pick around it.