From fcc8ae076d85aaae76544d9eea3f60d1aff75231 Mon Sep 17 00:00:00 2001 From: PlexSheep Date: Wed, 21 Feb 2024 23:05:33 +0100 Subject: [PATCH] fancier readme --- Cargo.toml | 2 +- README.md | 10 ++++++++++ 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/Cargo.toml b/Cargo.toml index aba419e..437b478 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -1,6 +1,6 @@ [package] name = "seep" -version = "0.1.0" +version = "0.1.1" edition = "2021" publish = true authors = ["Christoph J. Scherr "] diff --git a/README.md b/README.md index 33ccbfd..af56d57 100644 --- a/README.md +++ b/README.md @@ -1,10 +1,20 @@ # seep +![Project badge](https://img.shields.io/badge/language-Rust-blue.svg) +![Crates.io License](https://img.shields.io/crates/l/seep) +![Gitea Release](https://img.shields.io/gitea/v/release/PlexSheep/seep?gitea_url=https%3A%2F%2Fgit.cscherr.de) +![Gitea language count](https://img.shields.io/gitea/languages/count/PlexSheep/seep?gitea_url=https%3A%2F%2Fgit.cscherr.de) +[![cargo checks and tests](https://github.com/PlexSheep/seep/actions/workflows/cargo.yaml/badge.svg)](https://github.com/PlexSheep/seep/actions/workflows/cargo.yaml) + Print `stdin` to terminal, then pipe into next process. `seep` (short for see pipe and also to describe leaks in real pipes) has the purpose of letting you peek at what you're piping. +* [Original Repository](https://git.cscherr.de/PlexSheep/seep) +* [GitHub Mirror](https://github.com/PlexSheep/seep) +* [crates.io](https://crates.io/crates/seep) + ## Usage On Unix like systems, you can pass the output (`stdout`) of one process to the