@sentry/junior-github 0.87.0 → 0.89.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@sentry/junior-github",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.89.0",
|
|
4
4
|
"private": false,
|
|
5
5
|
"publishConfig": {
|
|
6
6
|
"access": "public"
|
|
@@ -24,7 +24,7 @@
|
|
|
24
24
|
],
|
|
25
25
|
"dependencies": {
|
|
26
26
|
"@sinclair/typebox": "^0.34.49",
|
|
27
|
-
"@sentry/junior-plugin-api": "0.
|
|
27
|
+
"@sentry/junior-plugin-api": "0.89.0"
|
|
28
28
|
},
|
|
29
29
|
"devDependencies": {
|
|
30
30
|
"@types/node": "^25.9.1",
|
|
@@ -132,7 +132,17 @@ Defaults:
|
|
|
132
132
|
|
|
133
133
|
**Assignment:** resolve GitHub handles from evidence (`gh api search/users`, org membership, repo history) before assigning requested reviewers or assignees. Skip assignment when the handle cannot be confirmed.
|
|
134
134
|
|
|
135
|
-
### 7.
|
|
135
|
+
### 7. Subscribe to PR lifecycle
|
|
136
|
+
|
|
137
|
+
After `github_createPullRequest` succeeds, check whether the result includes a subscribable resource hint. If it does, call `subscribeToResourceEvents` immediately before reporting.
|
|
138
|
+
|
|
139
|
+
- Use the suggested events from the hint; when absent, request review and CI events.
|
|
140
|
+
- Write a **self-contained intent** that captures repo, PR number, branch, and a single goal: resolve any review concerns and keep the build green. When an event fires, read the signal, address it, push, and report.
|
|
141
|
+
- **Only post an update when there is something meaningful to say.** Report when feedback has been addressed, a build failure has been fixed, the PR is fully green and ready to merge, or the PR has been merged. Stay silent on intermediate CI passes, queued checks, and informational events with no action taken.
|
|
142
|
+
|
|
143
|
+
If no subscribable hint is present, skip this step.
|
|
144
|
+
|
|
145
|
+
### 8. Report result
|
|
136
146
|
|
|
137
147
|
Return: repo, branch, PR URL/number (when applicable), checks run with results, pre-existing failures if any, checks not run and why.
|
|
138
148
|
|
|
@@ -52,6 +52,7 @@ Follow [references/research-rules.md](references/research-rules.md) for cross-ty
|
|
|
52
52
|
**Hard constraints — apply to every new issue:**
|
|
53
53
|
|
|
54
54
|
- Title ≤ 60 characters. Descriptive for bugs, imperative for tasks/features.
|
|
55
|
+
- **Issue title format: plain language, no type prefix.** Do not use `fix(x):`, `feat(x):`, `chore:`, `ref(x):`, or any other type-scope prefix — those belong in commit messages and PR titles, not issues.
|
|
55
56
|
- Summary ≤ 3 sentences. Do not restate the title in the body.
|
|
56
57
|
- Prefer flat bullet lists over headed sections for simple issues. Remove empty sections.
|
|
57
58
|
- Generalize session framing — strip channel references, slash commands, Slack thread IDs, user @mentions, and transcript fragments; replace with the underlying technical problem.
|