The change
A skipped pull request gets no comment.
An explained one still gets the watch link.
This pull request checks one behavior of the pull request explainer on v1.7.0. When the explainer skips a pull request, it should leave no comment at all. And when it does explain one, it should still post the watch link.
Two outcomes
Two outcomes, two different results.
Quiet
No comment on the pull request.
Watch link
The link is posted as a comment.
The explainer can end a run two ways. If it skips the pull request, the author's expectation is silence, with no comment left behind. If it explains the pull request, the run should still post the watch link, so a reviewer can open the presentation.
The diff
The whole diff is one line in one new file.
The change touches a single new file, named test-quiet-skip-check dot text. It adds one line, which says it is a test file for the quiet-skip check and should be deleted with the branch. Nothing else in the repository changes, so the file only gives the explainer a pull request to look at.
Not a change
"A test, not a change." It "will be closed and its branch deleted once the runs finish."
The title says it too: do not merge.
The author calls it a test, not a change, and says it will be closed and its branch deleted once the runs finish. The title adds the same instruction, do not merge. So this pull request exists to trigger runs, and it never reaches the main branch.
The evidence
The proof is in the runs, not in the pull request.
Check the skipped run left nothing on the pull request.
Check the explained run posted its link.
The description doesn't include before and after numbers or a recorded result. The evidence is whatever the workflow runs produce. Two things to look for. A skipped run that leaves the pull request without a comment, and an explained run that posts the watch link.
What to do
Nothing to review, nothing to merge.
One line, one test file, and a branch that gets deleted.
bisque-cloud/presenter · pull request 4
There is nothing here to review or merge. The pull request adds one line in a test file, and the branch goes away when the runs finish. If you want to see the result, open the workflow runs on pull request 4 in the presenter repository.
