ci: use apify/actions/pr-title-check wrapper for PR title checks#71
Merged
Conversation
github-actions
Bot
added
the
t-tooling
vdusek
approved these changes
Jun 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Replaces the direct
amannn/action-semantic-pull-requestusage in our PR-title workflow with the sharedapify/actions/pr-title-check@v1.3.0wrapper.Why
We're consolidating PR-title checking across the org behind a single wrapper action (apify/actions/pr-title-check). Benefits:
crate-ci/typos.Changes
amannn/action-semantic-pull-request@<version>step forapify/actions/pr-title-check@v1.3.0.GITHUB_TOKENenv wiring; the wrapper defaults togithub.token.Note
This adds a PR-title spell-check that wasn't running before. The spell-checker reads a
_typos.tomlthat lives in this repository — it's local to this repo, not a shared/org-wide config, so you have full control over it. If the check produces false positives, just add the offending words (or rules) to_typos.tomlin this repo. If no_typos.tomlis present, the typos defaults apply.