From 1585dc998623130112b965b1842368da7716364a Mon Sep 17 00:00:00 2001 From: Robert Kaussow Date: Sun, 27 Sep 2020 15:25:20 +0200 Subject: [PATCH] move credits --- README.md | 8 ++++---- docs/content/_index.md | 6 ++---- 2 files changed, 6 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 5b24706..62c399b 100644 --- a/README.md +++ b/README.md @@ -13,11 +13,9 @@ Another best practice scanner for Ansible roles and playbooks [![Source: GitHub](https://img.shields.io/badge/source-github-blue.svg?logo=github&logoColor=white)](https://github.com/thegeeklab/ansible-later) [![License: MIT](https://img.shields.io/github/license/thegeeklab/ansible-later)](https://github.com/thegeeklab/ansible-later/blob/master/LICENSE) -This is a fork of Will Thames [ansible-review](https://github.com/willthames/ansible-review) so credits goes to him for his work on ansible-review and ansible-lint. +ansible-later is a best practice scanner and linting tool. In most cases, if you write Ansible roles in a team, it helps to have a coding or best practice guideline in place. This will make Ansible roles more readable for all maintainers and can reduce the troubleshooting time. -_ansible-later_ is a best practice scanner and linting tool. In most cases, if you write Ansible roles in a team, it helps to have a coding or best practice guideline in place. This will make Ansible roles more readable for all maintainers and can reduce the troubleshooting time. - -_ansible-later_ does __not__ ensure that your role will work as expected. For Deployment test you can use other tools like [molecule](https://github.com/ansible/molecule). +ansible-later does __not__ ensure that your role will work as expected. For Deployment test you can use other tools like [molecule](https://github.com/ansible/molecule). You can find the full documentation at [https://ansible-later.geekdocs.de](https://ansible-later.geekdocs.de/). @@ -31,6 +29,8 @@ You can find the full documentation at [https://ansible-later.geekdocs.de](https Special thanks goes to all [contributors](https://github.com/thegeeklab/ansible-later/graphs/contributors). +ansible-later is a fork of Will Thames [ansible-review](https://github.com/willthames/ansible-review). Thanks for your work on ansible-review and ansible-lint. + ## License This project is licensed under the MIT License - see the [LICENSE](https://github.com/thegeeklab/ansible-later/blob/master/LICENSE) file for details. diff --git a/docs/content/_index.md b/docs/content/_index.md index e865059..e6cedb6 100644 --- a/docs/content/_index.md +++ b/docs/content/_index.md @@ -13,9 +13,7 @@ title: Documentation [![Source: GitHub](https://img.shields.io/badge/source-github-blue.svg?logo=github&logoColor=white)](https://github.com/thegeeklab/ansible-later) [![License: MIT](https://img.shields.io/github/license/thegeeklab/ansible-later)](https://github.com/thegeeklab/ansible-later/blob/master/LICENSE) -This is a fork of Will Thames [ansible-review](https://github.com/willthames/ansible-review) so credits goes to him for his work on ansible-review and ansible-lint. +ansible-later is a best practice scanner and linting tool. In most cases, if you write Ansible roles in a team, it helps to have a coding or best practice guideline in place. This will make Ansible roles more readable for all maintainers and can reduce the troubleshooting time. -_ansible-later_ is a best practice scanner and linting tool. In most cases, if you write Ansible roles in a team, it helps to have a coding or best practice guideline in place. This will make Ansible roles more readable for all maintainers and can reduce the troubleshooting time. - -_ansible-later_ does **not** ensure that your role will work as expected. For Deployment test you can use other tools +ansible-later does **not** ensure that your role will work as expected. For Deployment test you can use other tools like [molecule](https://github.com/ansible/molecule).