First runs stop failing
The first pull request explainer on a new repository no longer fails.
Version 1.5.1 fixes one failure. Run the pull request explainer on a new repository, on a runner that has no saved voice, and the job failed. Now the same step passes. The release notes put it in a single line: a run that narrated nothing now finishes without saving anything.
Why it failed
A run that never narrates leaves no models folder.
~/.bisque/models is missingThis starts when a run never gets as far as narrating. That is a pull request the explainer skipped, or a failure before narration. On a runner with no cached voice, such a run leaves no models folder behind. The step that names the installed speech models tripped over that missing folder. Now it names no models, nothing gets saved, and the job carries on.
The one-line fix
An empty key replaces the error.
v1.5.0
key=$(cd ~/.bisque/models 2>/dev/null && … | paste -sd+ -)
v1.5.1
key=$(cd ~/.bisque/models 2>/dev/null && … | paste -sd+ -) || key=""
The step builds a name from whatever is in the models folder. In 1.5.0 that line ends at the closing parenthesis, and a missing folder is an error. In 1.5.1 it ends with a fallback that sets the key to empty. An empty key names no models, so nothing is saved and the job finishes. The maintainers also left a comment above the step that says exactly this.
Two new workflows
The repository now explains its own pull requests.
explain-pull-requests.yml
Runs on every new pull request
Skips drafts, forks and Dependabot.
explain-on-mention.yml
Runs when you mention @bisque-cloud
Needs write access. Runs with network: deny.
This release also adds two workflows the project runs on itself, and they work as a template for your own setup. The first explains pull requests when they open, become ready for review, or reopen. It leaves out drafts, forks and Dependabot. The second covers forks. Someone with write access mentions bisque cloud in a comment, and the agent reads the stranger's text with no shell and no internet.
Nothing breaks
Nothing breaks. Nothing to migrate.
Nothing in this release breaks. The change to action.yml is three lines of comment, one edited line, and no changed inputs. A workflow that already passes behaves the same way. The only difference is on a runner where a run narrated nothing.
Upgrade
Pin v1.5.1 if you have hit this failure.
- uses: bisque-cloud/presenter@v1.5.0 + uses: bisque-cloud/presenter@v1.5.1
To upgrade, point your workflow at version 1.5.1. If you pin an exact tag, that means changing 1.5.0 to 1.5.1. If your runs already pass, this release changes nothing for them, so there is no hurry. What you get is a first pull request explainer on a new repository that finishes.
