From cbbfc3fb989c89c0a657833d6db4ac5586c1d375 Mon Sep 17 00:00:00 2001 From: Hernan Grecco Date: Fri, 12 May 2023 10:35:56 -0300 Subject: Moved Pint downtream Projects --- downstream_status.md | 17 +++++++++++++++++ pint/downstream_status.md | 17 ----------------- 2 files changed, 17 insertions(+), 17 deletions(-) create mode 100644 downstream_status.md delete mode 100644 pint/downstream_status.md diff --git a/downstream_status.md b/downstream_status.md new file mode 100644 index 0000000..d6d94db --- /dev/null +++ b/downstream_status.md @@ -0,0 +1,17 @@ +In Pint, we work hard to avoid breaking projects that depend on us. +If you are the maintainer of one of such projects, you can +help us get ahead of problems in simple way. + +In addition to your standard CI routines, create a CI that install Pint's +release candidates. You can also (or alternatively) create CI that install +Pint's master branch in GitHub. + +Take a look at the [Pint Downstream Demo](https://github.com/hgrecco/pint-downstream-demo) +if you need a template. + +Then, add your project badges to this file so it can be used as a Dashboard (always putting the stable first) + +[Pint Downstream Demo](https://github.com/hgrecco/pint-downstream-demo) +[![CI](https://github.com/hgrecco/pint-downstream-demo/actions/workflows/ci.yml/badge.svg)](https://github.com/hgrecco/pint-downstream-demo/actions/workflows/ci.yml) +[![CI-pint-pre](https://github.com/hgrecco/pint-downstream-demo/actions/workflows/ci-pint-pre.yml/badge.svg)](https://github.com/hgrecco/pint-downstream-demo/actions/workflows/ci-pint-pre.yml) +[![CI-master](https://github.com/hgrecco/pint-downstream-demo/actions/workflows/ci-master.yml/badge.svg)](https://github.com/hgrecco/pint-downstream-demo/actions/workflows/ci-master.yml) diff --git a/pint/downstream_status.md b/pint/downstream_status.md deleted file mode 100644 index d6d94db..0000000 --- a/pint/downstream_status.md +++ /dev/null @@ -1,17 +0,0 @@ -In Pint, we work hard to avoid breaking projects that depend on us. -If you are the maintainer of one of such projects, you can -help us get ahead of problems in simple way. - -In addition to your standard CI routines, create a CI that install Pint's -release candidates. You can also (or alternatively) create CI that install -Pint's master branch in GitHub. - -Take a look at the [Pint Downstream Demo](https://github.com/hgrecco/pint-downstream-demo) -if you need a template. - -Then, add your project badges to this file so it can be used as a Dashboard (always putting the stable first) - -[Pint Downstream Demo](https://github.com/hgrecco/pint-downstream-demo) -[![CI](https://github.com/hgrecco/pint-downstream-demo/actions/workflows/ci.yml/badge.svg)](https://github.com/hgrecco/pint-downstream-demo/actions/workflows/ci.yml) -[![CI-pint-pre](https://github.com/hgrecco/pint-downstream-demo/actions/workflows/ci-pint-pre.yml/badge.svg)](https://github.com/hgrecco/pint-downstream-demo/actions/workflows/ci-pint-pre.yml) -[![CI-master](https://github.com/hgrecco/pint-downstream-demo/actions/workflows/ci-master.yml/badge.svg)](https://github.com/hgrecco/pint-downstream-demo/actions/workflows/ci-master.yml) -- cgit v1.2.1