fix(ci): remove [skip ci] from automated commit messages#421
Merged
Conversation
Automated commits on dev (prerelease version bumps, back-merge re-entry) used the GitHub skip-ci flag in their messages to suppress CI reruns. However, GitHub scans the ENTIRE commit message body, not just the subject line — and standard merge commits to main auto-populate their body with the list of individual PR commits. This caused the skip flag to appear in the main merge commit body, suppressing ALL workflow triggers on every dev-to-main merge. Remove skip-ci flags from all automated commit messages in prerelease.yml and release.yml. Loop prevention is handled entirely by the existing job-level if conditions, which is the correct mechanism. Update the startsWith guard in release.yml to match the new commit message string. Root cause confirmed: PRs #410 and #419 both show zero workflow runs on main because their merge commit bodies contained skip-ci lines from automated dev commits.
perasperaactual
force-pushed
the
fix/skip-ci-leaking-into-main-merge-commits
branch
from
6a6da2c to
8b5f445
Compare
Contributor
✅ Visual Regression Test ResultsStatus: ✅ All visual tests passed! All screenshots match the baseline. No visual regressions detected! 🎉 |
Contributor
⚡ Performance Benchmark Results✅ Build Time Benchmarks: PASSED✅ Bundle Size Benchmarks: PASSED❌ Runtime Vitals Benchmarks: FAILED📝 Note: Detailed results are available in the job logs. 🎯 Performance Budgets:
Updated: 2026-05-15T17:02:25.088Z |
Contributor
♿ Accessibility Test ResultsOverall Status: ✅ 0/0 tests passed 🦮 WCAG 2.1 AA ComplianceNo WCAG test results available ⌨️ Keyboard NavigationNo keyboard navigation test results available 📊 Detailed ReportDownload the full HTML accessibility report from the workflow artifacts for:
🔍 Testing ChecklistOur accessibility tests verify:
Powered by @axe-core/playwright and Playwright |
This was referenced May 15, 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
1 participant
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.
Problem
Automated commits on
devused the GitHub skip-ci flag ([skip-ci]) in their messages to prevent CI reruns. However, GitHub scans the full commit message body, not just the subject line. Standard merge commits tomainauto-populate their body with a list of individual PR commits — so any skip-ci flag in a dev commit message leaks into the main merge commit body and suppresses all workflow triggers on that push, before any job-levelifconditions can run.Confirmed: PRs #410 and #419 both show zero workflow runs on
main(not even skipped entries) because their merge commit bodies contained skip-ci lines from automated dev commits.Fix
Remove skip-ci flags from all five automated commit messages across both workflow files. Loop prevention is handled entirely by the existing job-level
ifconditions, which is the correct mechanism.Also updates the
startsWithguard inrelease.ymlto match the new commit message string, so the loop-prevention logic stays in sync.Changes
prerelease.yml: removed skip-ci flag fromchore: bump prerelease versionsandchore: enter prerelease modecommitsrelease.yml: removed skip-ci flag fromchore: version packages for releaseandchore: re-enter prerelease mode after back-mergecommits; updated job-levelifcondition to matchTesting
The next dev→main merge after this lands will confirm workflows trigger correctly.
workflow_dispatchonrelease.ymlfrommaincan also verify end-to-end.