Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion .agents/skills/update-t3code/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -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,
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/update-t3code.yml
Original file line number Diff line number Diff line change
Expand Up @@ -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 }}).

Expand Down
4 changes: 4 additions & 0 deletions docs/publishing.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down