From 62180ff7dfbd396bef622ea10f10f18ee503cf43 Mon Sep 17 00:00:00 2001 From: Thomas Date: Sat, 7 Nov 2026 20:48:52 -0500 Subject: [PATCH] ci: title update PRs in the commit format --- .agents/skills/update-t3code/SKILL.md | 4 +++- .github/workflows/update-t3code.yml | 2 +- docs/publishing.md | 4 ++++ 3 files changed, 8 insertions(+), 2 deletions(-) diff --git a/.agents/skills/update-t3code/SKILL.md b/.agents/skills/update-t3code/SKILL.md index cbfe2d2..1547ed4 100644 --- a/.agents/skills/update-t3code/SKILL.md +++ b/.agents/skills/update-t3code/SKILL.md @@ -115,7 +115,9 @@ asked to. - **PR:** push to the PR branch, rewrite the description to cover the update and any packaging changes, mark it ready, and wait for **Validate Flatpak - update**. Bot-created runs need approval in the PR. + update**. Bot-created runs need approval in the PR. Keep the title in the + `type(scope): description` format, such as `fix(flatpak): ...` when packaging + fixes are the main change. - **Metainfo:** keep the release checker's formatting. Leave the release description empty for a plain upstream update. Write a short, specific note when the package itself changes. Packaging-only releases append a revision, diff --git a/.github/workflows/update-t3code.yml b/.github/workflows/update-t3code.yml index bab3e9a..68c3b78 100644 --- a/.github/workflows/update-t3code.yml +++ b/.github/workflows/update-t3code.yml @@ -55,7 +55,7 @@ jobs: # Bot-created PRs don't notify anyone unless a person is requested. reviewers: TB516 commit-message: "chore(flatpak): update T3 Code to ${{ steps.release.outputs.result }}" - title: Update T3 Code to ${{ steps.release.outputs.result }} + title: "chore(flatpak): update T3 Code to ${{ steps.release.outputs.result }}" body: | Update the pinned T3 Code release to [${{ steps.release.outputs.result }}](https://github.com/pingdotgg/t3code/releases/tag/${{ steps.release.outputs.result }}). diff --git a/docs/publishing.md b/docs/publishing.md index 250581e..c5f989b 100644 --- a/docs/publishing.md +++ b/docs/publishing.md @@ -18,6 +18,10 @@ Each release gets its own branch, such as `automation/update-t3code-v0.0.43`. The updater leaves an existing PR for that version alone, so newer releases can open separate PRs without overwriting patch fixes under review. +Squash-merging a PR with several commits uses its title as the commit +message, so PR titles use the `type(scope): description` format, such as +`chore(flatpak): update T3 Code to v0.1.7`. + **Validate Flatpak update** runs when packaging PRs are opened, updated, or reopened. It can also be started from the Actions tab. GitHub requires approval for runs triggered by the updater's `GITHUB_TOKEN`; approve them in the PR.