Replace travis with github actions

Author: vmihailenco

.github/dependabot.yml

@@ -0,0 +1,10 @@
+version: 2
+updates:
+  - package-ecosystem: gomod
+    directory: /
+    schedule:
+      interval: weekly
+  - package-ecosystem: github-actions
+    directory: /
+    schedule:
+      interval: weekly

.github/workflows/build.yml

@@ -0,0 +1,33 @@
+name: Go
+
+on:
+  push:
+    branches: [master]
+  pull_request:
+    branches: [master]
+
+jobs:
+  build:
+    name: build
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        go-version: [1.16.x]
+
+    services:
+      redis:
+        image: redis
+        options: >-
+          --health-cmd "redis-cli ping" --health-interval 10s --health-timeout 5s --health-retries 5
+        ports:
+          - 6379:6379
+
+    steps:
+      - name: Set up ${{ matrix.go-version }}
+        uses: actions/setup-go@v2
+
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Test
+        run: go test memqueue

.github/workflows/golangci-lint.yml

@@ -0,0 +1,19 @@
+name: golangci-lint
+
+on:
+  push:
+    tags:
+      - v*
+    branches:
+      - master
+      - main
+  pull_request:
+
+jobs:
+  golangci:
+    name: lint
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: golangci-lint
+        uses: golangci/golangci-lint-action@v2

.github/workflows/release.yml

@@ -0,0 +1,15 @@
+name: Releases
+
+on:
+  push:
+    tags:
+      - "v*"
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: ncipollo/release-action@v1
+        with:
+          body: Check CHANGELOG.md for details

.prettierrc

@@ -1,2 +1,2 @@
 proseWrap: always
-printWidth: 80
+printWidth: 100

.travis.yml

@@ -6,21 +6,20 @@
 
 # Golang asynchronous task/job queue with Redis, SQS, IronMQ, and in-memory backends
 
-[![Build Status](https://travis-ci.org/vmihailenco/taskq.svg)](https://travis-ci.org/vmihailenco/taskq)
-[![GoDoc](https://godoc.org/github.com/vmihailenco/taskq?status.svg)](https://pkg.go.dev/github.com/vmihailenco/taskq/v3?tab=doc)
+![build workflow](https://github.com/vmihailenco/taskq/actions/workflows/build.yml/badge.svg)
+[![PkgGoDev](https://pkg.go.dev/badge/github.com/vmihailenco/taskq/v3)](https://pkg.go.dev/github.com/vmihailenco/taskq/v3?tab=doc)
 
 ## Installation
 
 taskq supports 2 last Go versions and requires a Go version with
-[modules](https://github.com/golang/go/wiki/Modules) support. So make sure to
-initialize a Go module:
+[modules](https://github.com/golang/go/wiki/Modules) support. So make sure to initialize a Go
+module:
 
 ```shell
 go mod init github.com/my/repo
 ```
 
-And then install taskq/v3 (note _v3_ in the import; omitting it is a popular
-mistake):
+And then install taskq/v3 (note _v3_ in the import; omitting it is a popular mistake):
 
 ```shell
 go get github.com/vmihailenco/taskq/v3
@@ -29,16 +28,14 @@ go get github.com/vmihailenco/taskq/v3
 ## Features
 
 - Redis, SQS, IronMQ, and in-memory backends.
-- Automatically scaling number of goroutines used to fetch (fetcher) and process
-  messages (worker).
+- Automatically scaling number of goroutines used to fetch (fetcher) and process messages (worker).
 - Global rate limiting.
 - Global limit of workers.
 - Call once - deduplicating messages with same name.
 - Automatic retries with exponential backoffs.
 - Automatic pausing when all messages in queue fail.
 - Fallback handler for processing failed messages.
-- Message batching. It is used in SQS and IronMQ backends to add/delete messages
-  in batches.
+- Message batching. It is used in SQS and IronMQ backends to add/delete messages in batches.
 - Automatic message compression using snappy / s2.
 
 ## Quickstart
@@ -54,8 +51,8 @@ This way you can:
 - Scale API and worker separately.
 - Have different configs for API and worker (like timeouts).
 
-There is an [api_worker example](example/api_worker) that demonstrates this
-approach using Redis as a backend:
+There is an [api_worker example](example/api_worker) that demonstrates this approach using Redis as
+a backend:
 
 ```bash
 cd example/api_worker
@@ -166,33 +163,28 @@ for i := 0; i < 100; i++ {
 
 ## Message deduplication
 
-If a `Message` has a `Name` then this will be used as unique identifier and
-messages with the same name will be deduplicated (i.e. not processed again)
-within a 24 hour period (or possibly longer if not evicted from local cache
-after that period). Where `Name` is omitted then non deduplication occurs and
-each message will be processed. `Task`'s `WithMessage` and `WithArgs` both
-produces messages with no `Name` so will not be deduplicated. `OnceWithArgs`
-sets a name based off a consistent hash of the arguments and a quantised period
-of time (i.e. 'this hour', 'today') passed to `OnceWithArgs` a `period`. This
-guarantees that the same function will not be called with the same arguments
-during `period'.
+If a `Message` has a `Name` then this will be used as unique identifier and messages with the same
+name will be deduplicated (i.e. not processed again) within a 24 hour period (or possibly longer if
+not evicted from local cache after that period). Where `Name` is omitted then non deduplication
+occurs and each message will be processed. `Task`'s `WithMessage` and `WithArgs` both produces
+messages with no `Name` so will not be deduplicated. `OnceWithArgs` sets a name based off a
+consistent hash of the arguments and a quantised period of time (i.e. 'this hour', 'today') passed
+to `OnceWithArgs` a `period`. This guarantees that the same function will not be called with the
+same arguments during `period'.
 
 ## Handlers
 
-A `Handler` and `FallbackHandler` are supplied to `RegisterTask` in the
-`TaskOptions`.
+A `Handler` and `FallbackHandler` are supplied to `RegisterTask` in the `TaskOptions`.
 
 There are three permitted types of signature:
 
 1. A zero-argument function
-2. A function whose arguments are assignable in type from those which are passed
-   in the message
+2. A function whose arguments are assignable in type from those which are passed in the message
 3. A function which takes a single `*Message` argument
 
-If a task is registered with a handler that takes a Go `context.Context` as its
-first argument then when that handler is invoked it will be passed the same
-`Context` that was passed to `Consumer.Start(ctx)`. This can be used to transmit
-a signal to abort to all tasks being processed:
+If a task is registered with a handler that takes a Go `context.Context` as its first argument then
+when that handler is invoked it will be passed the same `Context` that was passed to
+`Consumer.Start(ctx)`. This can be used to transmit a signal to abort to all tasks being processed:
 
 ```go
 var AbortableTask = MainQueue.RegisterTask(&taskq.TaskOptions{
@@ -214,8 +206,8 @@ var AbortableTask = MainQueue.RegisterTask(&taskq.TaskOptions{
 
 ## Custom message delay
 
-If error returned by handler implements `Delay() time.Duration` interface then
-that delay is used to postpone message processing.
+If error returned by handler implements `Delay() time.Duration` interface then that delay is used to
+postpone message processing.
 
 ```go
 type RateLimitError string
@@ -235,9 +227,8 @@ func handler() error {
 
 ## Tracing
 
-taskq supports tracing out-of-the-box using
-[OpenTelemetry](https://opentelemetry.io/) API. To instrument a queue, use the
-following code:
+taskq supports tracing out-of-the-box using [OpenTelemetry](https://opentelemetry.io/) API. To
+instrument a queue, use the following code:
 
 ```go
 import "github.com/vmihailenco/taskq/extra/taskqotel/v3"
@@ -257,5 +248,4 @@ factory.Range(func(q taskq.Queue) bool {
 })
 ```
 
-We recommend using [Uptrace.dev](https://github.com/uptrace/uptrace-go) as a
-tracing backend.
+We recommend using [Uptrace.dev](https://github.com/uptrace/uptrace-go) as a tracing backend.

README.md

@@ -0,0 +1,15 @@
+# Releasing
+
+1. Run `release.sh` script which updates versions in go.mod files and pushes a new branch to GitHub:
+
+```shell
+TAG=v1.0.0 ./scripts/release.sh
+```
+
+2. Open a pull request and wait for the build to finish.
+
+3. Merge the pull request and run `tag.sh` to create tags for packages:
+
+```shell
+TAG=v1.0.0 ./scripts/tag.sh
+```

RELEASING.md

@@ -9,13 +9,13 @@ require (
 	github.com/dgryski/go-farm v0.0.0-20200201041132-a6ae2369ad13
 	github.com/go-redis/redis/v8 v8.11.2
 	github.com/go-redis/redis_rate/v9 v9.1.1
-	github.com/go-redis/redis/v8 v8.11.2 
 	github.com/golang/protobuf v1.4.3 // indirect
 	github.com/google/uuid v1.1.2
 	github.com/hashicorp/golang-lru v0.5.4
 	github.com/iron-io/iron_go3 v0.0.0-20190916120531-a4a7f74b73ac
 	github.com/jeffh/go.bdd v0.0.0-20120717032931-88f798ee0c74 // indirect
 	github.com/klauspost/compress v1.12.2
+	github.com/kr/pretty v0.2.1 // indirect
 	github.com/onsi/ginkgo v1.15.0
 	github.com/onsi/gomega v1.10.5
 	github.com/satori/go.uuid v1.2.0