Skip to content

Add CI check to ensure that gemspec is up to date #152

@movermeyer

Description

@movermeyer

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions