feat(.github): add Learning team message to high-priority-prs… (#15194)

* feat: add to high-priority-prs action to allow teams to get filtered PR results

* Update CODEOWNERS

* Update .github/actions/high-priority-prs/src/index.js

Co-Authored-By: Mike Allanson <michael.allanson@gmail.com>

.github/actions/high-priority-prs/README.md

@@ -1,18 +1,36 @@
 # high-priority-prs action
 
-Ported from @KyleAMathews [gatsby-pr-bot](https://github.com/KyleAMathews/gatsby-pr-bot/). [Read more about it on Kyle's blog](https://www.bricolage.io/bulding-a-slack-bot-to-help-handle-large-numbers-of-prs/)
+## Description
 
-Run locally [using act](https://github.com/nektos/act): `act -a "high-priority-prs"`
+Sends Slack messages [scheduled by GitHub actions](https://developer.github.com/actions/managing-workflows/workflow-configuration-options/#example-scheduled-workflow-block) with important PRs to respond to.
 
-See below for the original README.
+This is an experimental effort to help with identifying the PRs that most need responses — initially breaking them up into three queues, those that have:
 
----
+— never seen a response from core maintainers
 
-Sends Slack message every so often with important PRs to respond to.
+- had commits since the last comment so need a new review
+- not been updated for at least 30 days
 
-This is an experimental effort to help with identifying the PRs that most need responses — initially breaking them up into two queues — one for those that have never seen a response from core maintainers and those that have had commits since the last comment so need a new review.
+The goal is make sure every contributor has a great experience and to prevent valuable PRs from going stale.
 
-The goal is make sure every contributor has a great experience and to prevent valuable PRs from not getting in.
+Ported from @KyleAMathews gatsby-pr-bot. [Read more about it on Kyle's blog](https://www.bricolage.io/bulding-a-slack-bot-to-help-handle-large-numbers-of-prs/)
+
+## How it works
+
+Data is queried from GitHub and then filtered down to sort out information like whether or not maintainers have commented/reviewed
+a PR or not.
+
+The processed data is filtered down and sent out to teams that have been requested as reviewers (which is automated by the [CODEOWNERS](../../../CODEOWNERS) file),
+except for the Core team which receives a list from all open PRs.
+
+## Testing locally
+
+Run using [act](https://github.com/nektos/act): `act -a "high-priority-prs"`
+
+You'll be prompted to enter in the required tokens (GitHub will use the tokens saved from the UI), you can
+[generate your own Slack token](https://api.slack.com/custom-integrations/legacy-tokens) as well as [your own GitHub token](), for GitHub be sure to
+add permissions when generating for `repo`, `read:org`, and `read:discussion`, you can enter the ID of your personal slack channel to send direct messages
+to yourself while testing.
 
 ## Setup