You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Add PR workflow and align issue/discussion flows to reuse GitHub App tokens
- Update the notification script to report pull requests and skip internal authors via org membership checks
- Document the new workflow and internal-author suppression in the nexu-pal specs
Three GitHub Actions send Feishu webhook notifications for GitHub content:
61
+
Four GitHub Actions send Feishu webhook notifications for GitHub content:
61
62
62
-
1.**Issue notification** — On `issues: [opened]`, sends the existing issue card to the legacy webhook without changing the current chain.
63
+
1.**Issue notification** — On `issues: [opened]`, sends the existing issue card to the legacy webhook, but skips notifications when the author is a repository-owner organization member.
63
64
2.**Needs-triage issue notification** — On `issues: [labeled]`, when the added label is `needs-triage`, sends a triage card to either the bug or non-bug webhook based on the issue's current labels. The workflow maps GitHub secrets to internal env vars `BUG_WEBHOOK` and `REQ_WEBHOOK`.
64
-
3.**Discussion notification** — On `discussion: [created]`, sends the existing discussion card format using the discussion category in place of labels.
65
+
3.**Discussion notification** — On `discussion: [created]`, sends the existing discussion card format using the discussion category in place of labels, but skips notifications when the author is a repository-owner organization member.
66
+
4.**Pull request notification** — On `pull_request: [opened]`, sends the existing card format using pull request labels, but skips notifications when the author is a repository-owner organization member.
65
67
66
-
The legacy issue/discussion workflows continue to run `node scripts/notify/feishu-notify.mjs`. The new triage workflow runs `node scripts/notify/feishu-triage-notify.mjs`.
68
+
The issue/discussion/pull-request workflows run `node scripts/notify/feishu-notify.mjs`. The triage workflow runs `node scripts/notify/feishu-triage-notify.mjs`.
67
69
68
70
## Labels managed
69
71
@@ -81,7 +83,7 @@ The legacy issue/discussion workflows continue to run `node scripts/notify/feish
81
83
82
84
The three **nexu-pal** workflows create a short-lived token via `actions/create-github-app-token@v1` using secrets `NEXU_PAL_APP_ID` and `NEXU_PAL_PRIVATE_KEY_PEM`. All GitHub API calls and the first-interaction action use this App token.
83
85
84
-
The Feishu notification workflows do not use the GitHub App. They use the default GitHub Actions context plus Feishu incoming-webhook secrets.
86
+
The issue / discussion / pull-request Feishu notification workflows also create a short-lived GitHub App token so they can reuse the org-membership check and suppress notifications for internal authors. The `needs-triage` Feishu workflow continues to use GitHub Actions event data plus Feishu incoming-webhook secrets.
85
87
86
88
## Secrets
87
89
@@ -91,7 +93,7 @@ The Feishu notification workflows do not use the GitHub App. They use the defaul
0 commit comments