Pull requests

Branch names, titles, labels, and what ends up in the body.

Branch names, titles, commit messages, labels, the body format with release notes, and how reviewers and assignees are requested.

Branches

One branch is created per pull request, named from branch-prefix, which defaults to chore/quarto-extensions:

  • One extension: chore/quarto-extensions/update-<owner>-<name>-<version>, for example chore/quarto-extensions/update-mcanouil-iconify-3.0.2.
  • Grouped updates: chore/quarto-extensions/update-extensions-<YYYYMMDD>.

Because the branch name carries the target version, a pull request stays attached to the update it was opened for. An open pull request is matched on that branch name together with the exact title, and a match makes the run skip the update rather than rewrite the branch. A later run that finds a newer version therefore opens a pull request of its own, and the superseded one stays open until it is merged or closed.

Titles and commit messages

Titles and commit messages take their prefix from pr-title-prefix and commit-message-prefix, both defaulting to chore(deps)::

  • One extension: chore(deps): update owner/name extension to 1.2.3.
  • Several extensions: chore(deps): update 3 Quarto extensions.

Labels

The labels are exactly the comma-separated list given by pr-labels, which defaults to dependencies,quarto-extensions. No label is derived from the update type.

Body

The body groups the updates by type, quotes the release notes of each new version, and links back to the repository and the release:

Updates the following Quarto extension(s):

## 🐛 Patch Updates

- **[mcanouil/iconify](https://github.com/mcanouil/quarto-iconify)**: `3.0.0` → `3.0.2`

---

### Release Notes

<details>
<summary>Release 3.0.2</summary>

> ## What's Changed
>
> - refactor: use module and enhance iconify extension by @mcanouil in https://github.com/mcanouil/quarto-iconify/pull/46
> - ci: bump version for release :rocket: by @github-actions[bot] in https://github.com/mcanouil/quarto-iconify/pull/47
>
> **Full Changelog**: https://github.com/mcanouil/quarto-iconify/compare/3.0.1...3.0.2

</details>

**About**: Use Iconify icons in HTML-based Quarto documents (over 200,000 open source vector icons).

**Links**: [Repository](https://github.com/mcanouil/quarto-iconify) · [Release](https://github.com/mcanouil/quarto-iconify/releases/tag/3.0.2)

---

🤖 This PR was automatically generated by [quarto-extensions-updater](https://github.com/mcanouil/quarto-extensions-updater)

Extensions skipped during the run are listed in the body under a “Skipped Extensions” section, alongside the reason. See troubleshooting.

Reviewers and assignees

Three inputs cover team workflows:

  • pr-reviewers: individual GitHub users to request as reviewers.
  • pr-team-reviewers: GitHub team slugs to request as reviewers, which requires organisation membership.
  • pr-assignees: GitHub users to assign to the pull request.

Request individual reviewers:

- uses: mcanouil/quarto-extensions-updater@v2
  with:
    github-token: ${{ secrets.GITHUB_TOKEN }}
    pr-reviewers: "user1,user2"

Request team reviewers:

- uses: mcanouil/quarto-extensions-updater@v2
  with:
    github-token: ${{ secrets.GITHUB_TOKEN }}
    pr-team-reviewers: "frontend-team,backend-team"

Assign and request review at once:

- uses: mcanouil/quarto-extensions-updater@v2
  with:
    github-token: ${{ secrets.GITHUB_TOKEN }}
    pr-reviewers: "team-lead"
    pr-assignees: "dependency-manager"

Notes

  • Team reviewers require the repository to belong to an organisation, and the team to have access to it.
  • The token must carry the permissions needed to request reviewers and add assignees.
  • When branch protection requires approvals, auto-merge waits for them.
  • A failed reviewer or assignee request logs a warning, and the pull request is still created.
Back to top