Skipped pull requests get no comment
Skipped pull requests now get no comment.
Version 1.7.0 of the pull request explainer changes one thing you will see on every pull request it skips. When the explainer decides a pull request isn't worth walking through, it now leaves no comment at all. So a typo fix or a dependency bump stays quiet.
What the skipped comment used to say
Before, a skipped pull request got a comment. It opened with, "No explainer for this pull request," and then the one sentence reason, such as a lodash bump. Now that comment is gone. Pull requests the explainer does explain still get their watch link, exactly as before.
Where the skip reason goes
The reason moves to the run's log.
The reason doesn't disappear. In action.yml, the description of the skip-reason output used to say the sentence was posted on the pull request. Now it says it is not. The workflow keeps the reason in the run's log. And the skip-reason output still carries that one sentence, if a later step wants it.
What still posts
Two comments can still appear.
Two comments can still appear. The first is the watch link, posted on every pull request the explainer explains. The second is the setup note. If a run has no provider key, the pull request gets one comment naming the secret to add, and a later run edits that comment rather than adding another.
Skip comments from older versions
Old skip comments are still recognized.
Marks the skip comment older versions left. Skips are no longer posted, but one left by an earlier version is still a note that may be replaced.
If your pull requests already carry a skip comment from an earlier version, it isn't a problem. In judgment.ts the skip marker stays, with a new comment: skips are no longer posted, but one left by an earlier version is still a note that may be replaced.
Upgrade to v1.7.0
Upgrading needs no migration.
No explainer for this pull request comments to learn why.Upgrading takes one line, the new version tag. The diff changes no inputs and no workflow settings you need to touch. Point your workflow at version 1.7.0 and skipped pull requests go quiet. The one reason to wait is a team that reads those skip comments to see why a pull request was passed over. After this release, that answer is in the run's log.
