A gem for modernizing files in your Ruby project.
Please see the project documentation for more details.
- Getting Started - This guide explains how to update a Ruby gem with
bake-modernize, review the generated changes, and optionally migrate to releases through GitHub.
Please see the project releases for all releases.
- Provide agent context for updating gems and configuring GitHub releases.
- Ignore
[bot]authors in copyright attributions and gem authors. - Add opt-in
modernize:releases:githubmigration and omit redundant publishing hooks for gems usingbake-gem-github.
- Ignore
/vendor/bundleby default for dependencies installed by GitHub Actions' Bundler cache.
- Better
version.rbdetection inmodernize:gemspec.
- Make
modernize:releasespart of the defaultmodernizetask.
- Add support for automatic GitHub release generation.
- Improved copilot instructions for using agent context.
- Add
modernize:releasesto add release notes.
We welcome contributions to this project.
- Fork the repository.
- 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 a new pull request.
To run the test suite:
$ bundle exec susTo prepare a release branch and open a pull request from an up-to-date main:
$ bundle exec bake gem:github:release:patch # or minor or majorSee bake-gem-github for setup, remote releases, and recovery.
In order to protect users of this project, we require all contributors to comply with the Developer Certificate of Origin. This ensures that all contributions are properly licensed and attributed.
This project is best served by a collaborative and respectful environment. Treat each other professionally, respect differing viewpoints, and engage constructively. Harassment, discrimination, or harmful behavior is not tolerated. Communicate clearly, listen actively, and support one another. If any issues arise, please inform the project maintainers.