diff --git a/.goreleaser.yml b/.goreleaser.yml
new file mode 100644
index 0000000..b67576a
--- /dev/null
+++ b/.goreleaser.yml
@@ -0,0 +1,88 @@
+# This is an example goreleaser.yaml file with some sane defaults.
+# Make sure to check the documentation at http://goreleaser.com
+builds:
+- env:
+  - CGO_ENABLED=0
+checksum:
+  name_template: 'checksums.txt'
+snapshot:
+  name_template: "{{ .Tag }}-next"
+changelog:
+  sort: asc
+  filters:
+    exclude:
+    - '^docs:'
+    - '^test:'
+
+snapcraft:
+  # You can change the name of the package.
+  # Default: `{{ .ProjectName }}_{{ .Version }}_{{ .Os }}_{{ .Arch }}{{ if .Arm }}v{{ .Arm }}{{ end }}`
+  name_template: "{{ .ProjectName }}_{{ .Version }}_{{ .Os }}_{{ .Arch }}"
+
+  # Replacements for GOOS and GOARCH in the package name.
+  # Keys should be valid GOOSs or GOARCHs.
+  # Values are the respective replacements.
+  # Default is empty.
+  replacements:
+    amd64: 64-bit
+    386: 32-bit
+    darwin: macOS
+    linux: Tux
+
+  # The name of the snap. This is optional.
+  # Default is project name.
+  name: yamlfmt
+
+  # Wether to publish the snap to the snapcraft store.
+  # Remember you need to `snapcraft login` first.
+  # Defaults to false.
+  publish: true
+
+  # Single-line elevator pitch for your amazing snap.
+  # 79 char long at most.
+  summary: Formats yaml files.
+
+  # This the description of your snap. You have a paragraph or two to tell the
+  # most important story about your snap. Keep it under 100 words though,
+  # we live in tweetspace and your description wants to look good in the snap
+  # store.
+  description: |
+    Formats yaml files
+
+  # A guardrail to prevent you from releasing a snap to all your users before
+  # it is ready.
+  # `devel` will let you release only to the `edge` and `beta` channels in the
+  # store. `stable` will let you release also to the `candidate` and `stable`
+  # channels. More info about channels here:
+  # https://snapcraft.io/docs/reference/channels
+  grade: stable
+
+  # Snaps can be setup to follow three different confinement policies:
+  # `strict`, `devmode` and `classic`. A strict confinement where the snap
+  # can only read and write in its own namespace is recommended. Extra
+  # permissions for strict snaps can be declared as `plugs` for the app, which
+  # are explained later. More info about confinement here:
+  # https://snapcraft.io/docs/reference/confinement
+  confinement: strict
+
+  # Each binary built by GoReleaser is an app inside the snap. In this section
+  # you can declare extra details for those binaries. It is optional.
+  apps:
+
+    # The name of the app must be the same name as the binary built or the snapcraft name.
+    yamlfmt:
+
+      # If your app requires extra permissions to work outside of its default
+      # confined space, declare them here.
+      # You can read the documentation about the available plugs and the
+      # things they allow:
+      # https://snapcraft.io/docs/reference/interfaces.
+      #plugs: [""]
+
+      # If you want your app to be autostarted and to always run in the
+      # background, you can make it a simple daemon.
+      daemon: simple
+
+      # If you any to pass args to your binary, you can add them with the
+      # args option.
+      #args: --foo
diff --git a/.travis.yml b/.travis.yml
new file mode 100644
index 0000000..1ca29c5
--- /dev/null
+++ b/.travis.yml
@@ -0,0 +1,4 @@
+language: go
+
+go:
+  - "1.x"
diff --git a/README.md b/README.md
index 1d95f4a..ed3a346 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,7 @@
 # yamlfmt
 
+![Build Status](https://travis-ci.com/devopyio/yamlfmt.svg?branch=master)
+
 Formats yaml files.
 
 ## Install