Kwxm/update triage instructions (#7147)

* More things to monitor

* More things to monitor

* More things to monitor

* More things to monitor

* More things to monitor

* More things to monitor

* Try to convince link checker to accept OK link

* Reprioritise tasks slightly

Author: kwxm

doc/TRIAGE.md

@@ -6,10 +6,12 @@ This document elaborates on the triage process that we use to prioritize and res
 
 The triage person is responsible for monitoring the following places:
 
-- GitHub [issues](https://github.com/IntersectMBO/plutus/issues) and [PRs](https://github.com/IntersectMBO/plutus/pulls)
-- Plutus-related [CIPs](https://github.com/cardano-foundation/CIPs/pulls?q=is%3Apr+is%3Aopen+label%3A%22Category%3A+Plutus%22)
-- the [#plutus](https://input-output-rnd.slack.com/archives/C21UF2WVC) Slack channel
-- the [#plutus-working-group](https://discord.com/channels/1136727663583698984/1239888614796820531) Discord channel
+- Un-triaged [issues](https://github.com/IntersectMBO/plutus/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22status%3A%20needs%20triage%22) and external [PRs](https://github.com/IntersectMBO/plutus/pulls) in the [plutus](https://github.com/IntersectMBO/plutus) repository.  Note that this repository has a number of triage-related labels which whould be used as described [here](https://github.com/IntersectMBO/plutus/blob/master/doc/TRIAGE.md#labeling).
+- The `#plutus` [Slack channel](https://input-output-rnd.slack.com/archives/C21UF2WVC).
+- Plutus-related [CIPs](https://github.com/cardano-foundation/CIPs/pulls?q=is%3Apr+is%3Aopen+label%3A%22Category%3A+Plutus%22).
+- The [wg-plutus](https://discord.com/channels/1136727663583698984/1239888614796820531) Discord channel.
+- New [issues](https://github.com/IntersectMBO/plinth-template/issues) and external [PRs](https://github.com/IntersectMBO/plinth-template/pulls) in the [plinth-template](https://github.com/IntersectMBO/plinth-template) repository.
+- New Plutus-related [issues](https://github.com/cardano-scaling/cardano-blueprint/issues) and external [PRs](https://github.com/cardano-scaling/cardano-blueprint/pulls) in the [cardano-blueprint](https://github.com/cardano-scaling/cardano-blueprint) repository.
 
 ## Why
 
@@ -120,7 +122,7 @@ Do feel free to assign any issue to yourself if you want to track it and follow
 
 ### Labeling
 
-We use the GitHub labels feature. Reasons:
+We use the GitHub labels feature for new issues in the [plutus repository](https://github.com/IntersectMBO/plutus). Reasons:
 
 - For our own sake: a status label is easily accessible and makes it clear what the status of each issue is and whether it requires attention or not. You can even use labels in filter queries and specifically look for issues that may require attention (more on that below). Every single issue must have a `status: <something>` label.
 - For the sake of our users: a label succinctly summarizes how the team views the issue and whether to expect any action on it in the foreseeable future or not.

scripts/check-broken-links.sh

@@ -13,6 +13,7 @@ IGNORE_URLS=(
     https://www.haskell.org/cabal
     https://pvp.haskell.org
     https://github.com/cardano-foundation/CIPs/pulls\?q\=is%3Apr+is%3Aopen+label%3A%22Category%3A+Plutus%22
+    https://github.com/IntersectMBO/plutus/issues\?q\=is%3Aissue%20state%3Aopen%20label%3A%22status%3A%20needs%20triage%22
 )
 
 check_links() {