From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Kirill Yukhin <kyukhin@tarantool.org>
Cc: Alexander Turenko <alexander.turenko@tarantool.org>,
tarantool-patches@freelists.org,
"Alexander V . Tikhonov" <avtikhon@tarantool.org>
Subject: [tarantool-patches] [PATCH] readme: add GitLab-CI badge
Date: Fri, 30 Aug 2019 17:16:11 +0300 [thread overview]
Message-ID: <7965aaaa88e6eaf266d2e51776598ac05a4a6cde.1567174422.git.alexander.turenko@tarantool.org> (raw)
Aside of that fixed other badges URLs to point to master branch.
---
no issue
https://github.com/tarantool/tarantool/tree/Totktonada/add-gitlab-ci-badge
I had added [1] instead of [2], because the latter looks as a mess. [1]
shows CI statuses for master branch.
[1]: https://gitlab.com/tarantool/tarantool/commits/master
[2]: https://gitlab.com/tarantool/tarantool/pipelines
README.md | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/README.md b/README.md
index 020f79815..b682cabeb 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,7 @@
# Tarantool
[![Build Status][travis-badge]][travis-url]
+[![Build Status][gitlab-ci-badge]][gitlab-ci-url]
[![Code Coverage][coverage-badge]][coverage-url]
[![Telegram][telegram-badge]][telegram-url]
[![Slack][slack-badge]][slack-url]
@@ -52,10 +53,12 @@ list, tarantool@googlegroups.com.
Thank you for your interest in Tarantool!
-[travis-badge]: https://api.travis-ci.org/tarantool/tarantool.svg?branch=2.1
+[travis-badge]: https://api.travis-ci.org/tarantool/tarantool.svg?branch=master
[travis-url]: https://travis-ci.org/tarantool/tarantool
-[coverage-badge]: https://coveralls.io/repos/github/tarantool/tarantool/badge.svg?branch=2.1
-[coverage-url]: https://coveralls.io/github/tarantool/tarantool?branch=2.1
+[gitlab-ci-badge]: https://gitlab.com/tarantool/tarantool/badges/master/pipeline.svg
+[gitlab-ci-url]: https://gitlab.com/tarantool/tarantool/commits/master
+[coverage-badge]: https://coveralls.io/repos/github/tarantool/tarantool/badge.svg?branch=master
+[coverage-url]: https://coveralls.io/github/tarantool/tarantool?branch=master
[groups-badge]: https://img.shields.io/badge/Google-Groups-orange.svg
[groups-url]: https://groups.google.com/forum/#!forum/tarantool
[telegram-badge]: https://img.shields.io/badge/Telegram-join%20chat-blue.svg
--
2.22.0
reply other threads:[~2019-08-30 14:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7965aaaa88e6eaf266d2e51776598ac05a4a6cde.1567174422.git.alexander.turenko@tarantool.org \
--to=alexander.turenko@tarantool.org \
--cc=avtikhon@tarantool.org \
--cc=kyukhin@tarantool.org \
--cc=tarantool-patches@freelists.org \
--subject='Re: [tarantool-patches] [PATCH] readme: add GitLab-CI badge' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox