Update references to Travis in docs

client-spec/clarity
Owen Voke 2020-06-09 11:32:38 +01:00 committed by Marco Bonelli
parent bcab713a65
commit 2126dfec04
2 changed files with 4 additions and 4 deletions

View File

@ -1,14 +1,14 @@
<div align="center"> <div align="center">
<h1><img alt="tldr-pages" src="images/banner-light.png" width=600/></h1> <h1><img alt="tldr-pages" src="images/banner-light.png" width=600/></h1>
[![Build status][travis-image]][travis-url] [![Build status][github-actions-image]][github-actions-url]
[![Gitter chat][gitter-image]][gitter-url] [![Gitter chat][gitter-image]][gitter-url]
[![Merged PRs][prs-merged-image]][prs-merged-url] [![Merged PRs][prs-merged-image]][prs-merged-url]
[![GitHub contributors][contributors-image]][contributors-url] [![GitHub contributors][contributors-image]][contributors-url]
[![license][license-image]][license-url] [![license][license-image]][license-url]
[travis-url]: https://travis-ci.org/tldr-pages/tldr/builds [github-actions-url]: https://github.com/tldr-pages/tldr/actions
[travis-image]: https://travis-ci.org/tldr-pages/tldr.svg?branch=master [github-actions-image]: https://img.shields.io/github/workflow/status/tldr-pages/tldr/CI.svg
[gitter-url]: https://gitter.im/tldr-pages/tldr [gitter-url]: https://gitter.im/tldr-pages/tldr
[gitter-image]: https://img.shields.io/badge/chat-on_gitter-deeppink [gitter-image]: https://img.shields.io/badge/chat-on_gitter-deeppink
[prs-merged-url]: https://github.com/tldr-pages/tldr/pulls?q=is:pr+is:merged [prs-merged-url]: https://github.com/tldr-pages/tldr/pulls?q=is:pr+is:merged

View File

@ -55,7 +55,7 @@ as a guideline for current and future maintainers.
## II. Handling PRs ## II. Handling PRs
- PRs should be merged once they - PRs should be merged once they
(1) **pass the automated tests** (Travis CI, CLA signing, etc.), (1) **pass the automated tests** (GitHub Actions, CLA signing, etc.),
(2) have the **review comments addressed**, and (2) have the **review comments addressed**, and
(3) get **approved reviews by two maintainers** (3) get **approved reviews by two maintainers**
(the second maintainer can perform the merge immediately after accepting.) (the second maintainer can perform the merge immediately after accepting.)