ruby-i18n / ruby-i18n/ruby-cldr
Add CI check to ensure that gemspec is up to date
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 78
- Forks
- 18
- Avg merge
- 9d 8h
- Merged PRs (30d)
- 3
Description
Problem
ruby-cldr.gemspec is auto-generated by bundle exec rake gemspec (via Jeweler).
However, developers will forget to run it as part of their PRs. Which means that we risk releasing a gem without all the required files, for example.
Potential solutions
a) add it to the checklist in the PR template
b) add a CI check that fails if bundle exec rake gemspec && rubocop -a ruby-cldr.gemspec produces any differences.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with ruby-cldr.gemspec, the Jeweler gemspec entry point, and the repository's CI configuration. Run bundle exec rake gemspec && rubocop -a ruby-cldr.gemspec and inspect how generated differences are detected. Done means CI reliably fails when the generated gemspec differs from the committed file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100