zwave-js / zwave-js-ui / 30358332220

12%

push

github

fix(bot): run triage on transferred issues (#4762)

Port of zwave-js/zwave-js#8982, for issues transferred the other way.

Transferring an issue recreates the source repo's comments in the
destination with their original timestamps, and `zwave-js` runs a
mirrored copy of these scripts that stamps the same marker tags. So the
docs answer and the wrong-repo notice both considered themselves done
and stayed silent, and nothing on a transferred comment identifies where
it came from. The `transferred` timeline event is the one usable signal.

- New `utils.cjs` with `listCommentsSinceTransfer()`, which lists an
issue's comments and drops everything older than the last transfer.
`answerFromDocs` and `classifyIssueFeedback` use it instead of their own
lookups.
- Bot comments inherited from the other repo are collapsed as outdated —
they are about the wrong repository now.
- The nightly feedback digest no longer scores a foreign answer as one
of ours, where reactions to it could suppress unrelated future answers.

Discussions keep the old behavior; they have no timeline API, so an
inherited answer there still counts as answered.

Verified with unit tests plus a full 180-day digest run against the live
repo, which produces identical records to the current code.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude <noreply@anthropic.com>

495 of 4531 branches covered (10.92%)

Branch coverage included in aggregate %.

947 of 7002 relevant lines covered (13.52%)

2.09 hits per line