CONTRIBUTING.md

Contributing

Hi there! We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.

Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.

Submitting a pull request

0. Fork and clone the repository
1. Configure and install the dependencies: script/bootstrap
2. Setup test fixtures: bundle exec rake setup
3. Make sure the tests pass on your machine: bundle exec rake test
4. Create a new branch: git checkout -b my-branch-name
5. Make your change, add tests, and make sure the tests still pass
6. Push to your fork and submit a pull request
7. Pat your self on the back and wait for your pull request to be reviewed and merged.

Here are a few things you can do that will increase the likelihood of your pull request being accepted:

• Follow the style guide.
• Write tests.
• Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
• Write a good commit message.

Adding a new Dependency Source

Pull requests that include a new dependency source must also

• Include documentation for the new source and update the documented source list.
• Add a setup script if needed.
• Include tests and test fixtures needed to verify the source in CI.
• Add a CI job to .github/workflows/test.yml.

Releasing

If you are the current maintainer of this gem:

1. Create a branch for the release: git checkout -b cut-release-xx.xx.xx
2. Make sure your local dependencies are up to date: script/bootstrap
3. Ensure that tests are green: bundle exec rake test
4. Bump gem version in lib/licensed/version.rb.
5. Update CHANGELOG.md
6. Make a PR to github/licensed.
7. Build a local gem: bundle exec rake build
8. Test the gem:
   1. Bump the Gemfile and Gemfile.lock versions for an app which relies on this gem
   2. Install the new gem locally
   3. Test behavior locally, branch deploy, whatever needs to happen
9. Merge github/licensed PR
10. Create a new github/licensed release

• Set the release name and tag to the release version - x.xx.x
• Set the release body to the changelog entries for the release

The following steps will happen automatically from a GitHub Actions workflow after creating the release. In case that fails, the following steps can be performed manually

11. Push the gem from (7) to rubygems.org -- gem push licensed-x.xx.xx.gem

Resources

• How to Contribute to Open Source
• Using Pull Requests
• GitHub Help