summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorHernan Grecco <hgrecco@gmail.com>2023-05-12 10:34:22 -0300
committerHernan Grecco <hgrecco@gmail.com>2023-05-12 10:34:22 -0300
commit70269f352a922c5e796183a56e6a4e336a5845bb (patch)
treefe6ec4812b6b24e023f1ee75ffc8090b7e722446
parent2a89a4423f0bf6e4ffd6179170aae9c475b61643 (diff)
downloadpint-70269f352a922c5e796183a56e6a4e336a5845bb.tar.gz
Started downstream status page
-rw-r--r--pint/downstream_status.md17
1 files changed, 17 insertions, 0 deletions
diff --git a/pint/downstream_status.md b/pint/downstream_status.md
new file mode 100644
index 0000000..d6d94db
--- /dev/null
+++ b/pint/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)