Skip to content

CI: run rspec and rubocop on every pull request - #106

Merged
fatbeard2 merged 2 commits into
masterfrom
ci/test-workflow
Sep 22, 2026
Merged

fatbeard2 merged 2 commits into
masterfrom
ci/test-workflow

Conversation

@fatbeard2

Copy link
Copy Markdown
Contributor

Why?

The repo only had the manual "Publish Gem" workflow, so the spec suite ran wherever someone remembered to run it. kb-ruby#105 was verified in a local Docker container and nowhere else. Every pull request should run the suite.

Changes

  • .github/workflows/ci.yml: two jobs on every pull request and on pushes to master, both on Ruby 3.4 (what connected_health and Global Admin run): bundle exec rubocop lib spec and bundle exec rspec. Bundler cache via ruby/setup-ruby.
  • README gains a short Development section with the local Docker commands.

No matrix on purpose; one Ruby keeps it fast and the gem's required_ruby_version already documents the supported range.

Checklist

  • Tests added/updated (not applicable)
  • README file updated
  • Changelog updated (not applicable, no gem change)
  • Version file lib/kb/version.rb updated (not applicable)

How to test

This PR's own checks: the CI workflow runs against this branch and must be green. Then rebase #105 onto it to see the suite run there too.

🤖 Generated with Claude Code

fatbeard2 and others added 2 commits September 22, 2026 15:29
The repo only had the manual release workflow, so the suite ran wherever
someone remembered to run it. Ruby 3.4, matching connected_health and
Global Admin.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@fatbeard2
fatbeard2 merged commit 1feba3b into master Sep 22, 2026
2 checks passed
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