Skip to content

Commit f72466e

Browse files
authored
Merge pull request #165 from pusher/github-actions
Use Github Actions instead of Travis
2 parents 2b32282 + a6cfec1 commit f72466e

File tree

3 files changed

+36
-20
lines changed

3 files changed

+36
-20
lines changed

.github/workflows/test.yml

Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
name: Tests
2+
3+
on: [push, pull_request]
4+
5+
jobs:
6+
test:
7+
runs-on: ubuntu-20.04
8+
strategy:
9+
fail-fast: false
10+
matrix:
11+
ruby: [ '2.4', '2.5', '2.6' ]
12+
13+
name: Ruby ${{ matrix.ruby }} Test
14+
15+
env:
16+
DAY_OF_WEEK: Mon
17+
18+
steps:
19+
- name: Checkout
20+
uses: actions/checkout@v2
21+
22+
- name: Setup Ruby
23+
uses: ruby/setup-ruby@v1
24+
with:
25+
ruby-version: ${{ matrix.ruby }}
26+
27+
- name: Install dependencies
28+
run: bundle install
29+
30+
- name: Run test suite
31+
run: bundle exec rake

.travis.yml

Lines changed: 0 additions & 16 deletions
This file was deleted.

README.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,11 @@
22

33
This Gem provides a Ruby interface to [the Pusher HTTP API for Pusher Channels](https://pusher.com/docs/channels/library_auth_reference/rest-api).
44

5-
[![Build Status](https://secure.travis-ci.org/pusher/pusher-http-ruby.svg?branch=master)](http://travis-ci.org/pusher/pusher-http-ruby) [![Gem Version](https://badge.fury.io/rb/pusher.svg)](https://badge.fury.io/rb/pusher)
5+
[![Build Status](https://github.com/pusher/pusher-http-ruby/workflows/Tests/badge.svg)](https://github.com/pusher/pusher-http-ruby/actions?query=workflow%3ATests+branch%3Amaster) [![Gem Version](https://badge.fury.io/rb/pusher.svg)](https://badge.fury.io/rb/pusher)
6+
7+
## Supported Platforms
8+
9+
* Ruby - supports **Ruby 2.4 or greater**.
610

711
## Installation and Configuration
812

@@ -295,6 +299,3 @@ pusher.trigger(
295299
```
296300

297301
Rationale: the methods in this library map directly to individual Channels HTTP API requests. If we allowed triggering a single event on multiple channels (some encrypted, some unencrypted), then it would require two API requests: one where the event is encrypted to the encrypted channels, and one where the event is unencrypted for unencrypted channels.
298-
299-
## Supported Ruby versions
300-
2.4+

0 commit comments

Comments
 (0)