Skip to content

chore: add Rakefile as alternative CI tooling#571

Draft
quartzmo wants to merge 1 commit into
googleapis:mainfrom
quartzmo:add-rakefile
Draft

chore: add Rakefile as alternative CI tooling#571
quartzmo wants to merge 1 commit into
googleapis:mainfrom
quartzmo:add-rakefile

Conversation

@quartzmo
Copy link
Copy Markdown
Member

Offer a Rakefile as an alternative to the current Toys-based CI tooling to improve simplicity and maintainability in this relatively small repository.

  • Encountered a failure in toys spec in CI due to dependency resolution issues with the local gem (see chore: add test comment to verify CI failures #570).
  • Added Rakefile with equivalents for all Toys tasks.
  • Added a separate verification workflow .github/workflows/rake_ci.yml for Ruby 3.4.

@quartzmo quartzmo force-pushed the add-rakefile branch 3 times, most recently from cde6c01 to 5ba363a Compare May 22, 2026 23:40
Offer a Rakefile as an alternative to the current Toys-based CI tooling to improve simplicity and maintainability in this relatively small repository.

* Encountered a failure in `toys spec` in CI due to dependency resolution issues with the local gem (see googleapis#570).
* Added Rakefile with equivalents for all Toys tasks.
* Added a separate verification workflow `.github/workflows/rake_ci.yml` for Ruby 3.4.
* Added `vendor/**/*` to RuboCop excludes to prevent inspecting gem dependencies in CI (which Toys handled implicitly).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant