summaryrefslogtreecommitdiff
path: root/libpod/container_internal_linux.go
diff options
context:
space:
mode:
authorChris Evich <cevich@redhat.com>2018-11-14 10:15:14 -0500
committerChris Evich <cevich@redhat.com>2018-11-14 10:23:53 -0500
commit1fb3851620aa63139556a7e93d27234d8b010ecc (patch)
tree6864b35bdfa0cc3f10837fdb38fef3187e449b71 /libpod/container_internal_linux.go
parent2b911b0c8a51877f75cafde5d2ebb54ad31df410 (diff)
downloadpodman-1fb3851620aa63139556a7e93d27234d8b010ecc.tar.gz
podman-1fb3851620aa63139556a7e93d27234d8b010ecc.tar.bz2
podman-1fb3851620aa63139556a7e93d27234d8b010ecc.zip
Cirrus: Add master branch testing status badge
Engineers get testing status via their PR's but another round of testing happens post-merge, without any direct feedback. Fix this in a small way, by adding a dynamic status badge on the front-page. If this turns red, it means Cirrus-CI testing of the master branch failed for some reason. Nearly always it's something harmless, but once and a while, this catches really nasty problems caused by merge-sequence issues. Having that feedback on the front page ensures the right people will eventually get called into action. Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'libpod/container_internal_linux.go')
0 files changed, 0 insertions, 0 deletions