This is only a template to create other gems.
Run ./rename.sh CLASS_NAME
to rename the files, after that, you can erase it.
Example:
./rename.sh Foo::Bar
- Create your repository using this repo as template
- Change some files:
- Path /lib/mygem -> Change for you path directoy.
- E.g: /lib/foo/bar
- File /lib/mygem -> Change for your main module name
- Don't forget to create a file rb in /lib for Rails default import
- E.g: For a gem called activemessage-core and the main module is ActiveMessage::Core, create a file in /lib called activemessage-core.rb and require 'active_message/core' inside that
- Don't forget to create da main module nested
- E.g: For a module ActiveMessage::Core, it should be /lib/active_message/core.rb
- Don't forget to create a file rb in /lib for Rails default import
- Change gem name in /bin/console
- Change spec mygem_spec.rb
- Chagem gem name in spec_helper.rb
- Change gemspec
- Filename
- Summary
- Description
- Dependecies
- Delete README.md and rename README-template.md to README.md and change its content
- Change the follow variables:
- CHANGE_MY_NAME_PLEASE
- CHANGE_MY_DESCRIPTION_PLEASE
- CHANGE_MY_GEM_NAME_PLEASE
- CHANGE_MY_INSTALLATION_PLEASE
- CHANGE_MY_SETTINGS_PLEASE
- CHANGE_MY_REPO_NAME_PLEASE
- CHANGE_MY_CODE_CLIMATE_ACCOUNT_PLEASE
- Change the follow variables:
- Delete rename.sh
- Change code climate key in file .travis.yml
- Run bundle && bundle exec rubocop && bundle exec rspec to check if everything is ok
- Fork it
- Create your feature branch (git checkout -b my-new-feature)
- Commit your changes (git commit -am 'Add some feature')
- Push to the branch (git push origin my-new-feature)
- Create new Pull Request
The gem is available as open source under the terms of the MIT License.
Everyone interacting in the Rails::Healthcheck project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.