Skip to main content

Troubleshooting

When a run reports nothing, or less than expected.

What to check when no extensions are found, no updates are detected, no pull request appears, or an extension is skipped during a run.

No extensions found

Extensions must sit in _extensions/owner/name/ with an _extension.yml or _extension.yaml manifest. When the Quarto sub-projects live in sub-directories, list them through scan-directories; only the workspace root is scanned by default.

No updates detected

• Confirm the extension is in the registry: https://m.canouil.dev/quarto-extensions/.
• Confirm each manifest carries a version field and a source field; an extension without a source is skipped, because there is nothing to track.
• Confirm the versions follow semantic versioning (X.Y.Z).
• Confirm the update strategy and the include and exclude lists are not filtering out the update.

Pull request not created

• Confirm the workflow grants contents: write and pull-requests: write.
• Confirm create-pr is not false, and dry-run is not true.
• Check the workflow logs for API errors.
• Check that no pull request is already open with the same branch and title, since that update is then skipped rather than opened again.

Extensions skipped

An extension can be skipped during an update for two reasons:

• The Quarto version requirement is not met. The updated extension declares a quarto-required that exceeds the Quarto version installed in the workflow. Raise the version in the setup step, or wait for a compatible extension release.
• quarto add failed. The Quarto CLI could not install the extension, for example because of a network error or an invalid release. The specific error is in the workflow logs.

Skipped extensions are reported in the job summary and, where applicable, in the pull request body under a “Skipped Extensions” section. A skipped extension does not fail the run: the other extensions are still processed.

Auto-merge not enabled

GitHub refuses auto-merge unless the base branch has at least one required status check or branch protection rule. The pull request is still created, and the action logs a warning. See auto-merge.