diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
index bd88488..e6a185a 100644
--- a/.github/workflows/build.yml
+++ b/.github/workflows/build.yml
@@ -11,14 +11,14 @@ on:
     
   push:
     branches:
-      - development
+      - master
   
 jobs:
   build:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        smalltalk: [ Pharo64-12, Pharo64-11, Pharo64-10 ]
+        smalltalk: [ Pharo64-11, Pharo64-10 ]
     name: ${{ matrix.smalltalk }}
     steps:
       - uses: actions/checkout@v2
diff --git a/README.md b/README.md
index 214a0bd..aeda737 100644
--- a/README.md
+++ b/README.md
@@ -1,8 +1,6 @@
 SnapDump
 ========
 
-[![Build Status](https://travis-ci.com/zweidenker/SnapDump.svg?branch=master)](https://travis-ci.com/zweidenker/SnapDump)
-
 SnapDump is a software for pharo to create and manage runtime snapshots. When developing software in pharo and an exception occurs we get a debugger window openend. This is not possible if the application is deployed in a server environment. Usually activity of a server is written in logfiles but logfiles are a very poor way of getting error feedback from your application. In pharo we can snapshot the state of the application when an exception occurs. This snapshot can be serialized using the fuel graph serializer and uploaded to a server. By uploading the snapshot to a server we can use SnapDump in a distributed scenario where multiple servers give feedback.
 
 Terminology