@sentry/junior-github 0.33.0 → 0.35.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
|
@@ -20,7 +20,8 @@ Repository checkout, source-code investigation, and pull request operations via
|
|
|
20
20
|
### 1. Resolve operation and target
|
|
21
21
|
|
|
22
22
|
- Determine whether the task is `clone`, `source-code investigation`, a pull request inspection (`view`, `list`, `diff`, `checks`), or a pull request mutation (`create`, `update`, `close`, `merge`).
|
|
23
|
-
- Resolve repository
|
|
23
|
+
- Resolve repository from the requested action: explicit target wins; otherwise use `<configuration>` `github.repo`. If absent, run standalone `jr-rpc config get github.repo`.
|
|
24
|
+
- Preserve non-target GitHub references when they materially support the work.
|
|
24
25
|
- Run `jr-rpc config get github.repo` as its own bash command. Do not combine it with `cd`, `&&`, pipes, or any `gh` or `git` command.
|
|
25
26
|
- After resolving a configured repo, pass it explicitly to the next `gh` command with `--repo owner/repo`; do not rely on implicit GitHub CLI repository discovery.
|
|
26
27
|
- Resolve the pull request number for operations targeting an existing PR.
|
|
@@ -22,7 +22,8 @@ Use only for GitHub issues. For pull requests, branches, pushes, or PR auth-orde
|
|
|
22
22
|
### 1. Resolve operation and target
|
|
23
23
|
|
|
24
24
|
- Determine whether the task is `create`, `update`, `comment`, `labels`, `state`, or read-only inspection.
|
|
25
|
-
- Resolve repository
|
|
25
|
+
- Resolve repository from the requested action: explicit target wins; otherwise use `<configuration>` `github.repo`. If absent, run standalone `jr-rpc config get github.repo`.
|
|
26
|
+
- Preserve non-target GitHub references that materially support created issue or comment bodies.
|
|
26
27
|
- Run `jr-rpc config get github.repo` as its own bash command. Do not combine it with `cd`, `&&`, pipes, or any `gh` command.
|
|
27
28
|
- After resolving a configured repo, pass it explicitly to the next `gh` command with `--repo owner/repo`; do not rely on implicit GitHub CLI repository discovery.
|
|
28
29
|
- Resolve the issue number for non-create operations.
|
|
@@ -57,6 +58,7 @@ Follow [references/research-rules.md](references/research-rules.md) for cross-ty
|
|
|
57
58
|
- Generalize session framing — strip channel references, slash commands, Slack thread IDs, user @mentions, and transcript fragments; replace with the underlying technical problem.
|
|
58
59
|
- Compress source material. Research notes, hypotheses, or transcripts become a short summary + scoped bullets — never paste raw investigation into the body.
|
|
59
60
|
- Do not add desired outcome, expected behavior, or acceptance criteria unless the thread explicitly requests them.
|
|
61
|
+
- Preserve material source references inline.
|
|
60
62
|
- When the request originated from a Slack thread or any on-behalf-of context, append a final line `Action taken on behalf of <name>.` using the action requester's real name. The action requester is the current `<requester>` or the person who explicitly asked you to create/update the issue, not necessarily the original reporter.
|
|
61
63
|
|
|
62
64
|
**Attribution:**
|