Skip to content

Remove [skip ci] from bot commit message in CD release#720

Merged
CasperWA merged 1 commit into
masterfrom
cwa/fix-skip-ci
Apr 21, 2026
Merged

Remove [skip ci] from bot commit message in CD release#720
CasperWA merged 1 commit into
masterfrom
cwa/fix-skip-ci

Conversation

@CasperWA

@CasperWA CasperWA commented Apr 21, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Removes [skip ci] from the [bot] Update version and CHANGELOG commit message in cd_release.yml.

Why

[skip ci] in a commit message suppresses all CI runs triggered by that push — including runs on the push-action/** temp branch that CasperWA/push-protected creates while waiting for status checks to pass. With no CI running on the temp branch, push-protected finds 0 status check runs, immediately declares them "all complete," then attempts to push to master — which GitHub rejects with "7 of 7 required status checks are expected".

Removing [skip ci] lets ci_tests.yml run normally on the push-action/** branch (it already has an explicit push-action/** trigger for exactly this purpose), allowing push-protected to wait for and confirm all required checks before pushing.

Test plan

  • Confirm the next CD release run completes successfully end-to-end (version bump commit → temp branch CI passes → push to master succeeds).
Click to view squash commit message

Remove skip-ci token from bot commit message

The skip-ci token suppresses CI on the push-action/** temp branch that
push-protected creates, so GitHub finds 0 status check runs and
immediately tries to merge — which then fails with "7 of 7 required
status checks are expected".

The skip-ci token suppresses CI on the push-action/** temp branch that
push-protected creates, so GitHub finds 0 status check runs and
immediately tries to merge — which then fails with "7 of 7 required
status checks are expected".

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the CD release workflow to ensure required CI checks run during protected-branch updates performed via CasperWA/push-protected, avoiding the “required status checks are expected” failure caused by skipping CI.

Changes:

  • Remove [skip ci] from the bot commit message in the CD release workflow.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@codecov

codecov Bot commented Apr 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.34%. Comparing base (03e2734) to head (d1fde92).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #720   +/-   ##
=======================================
  Coverage   84.34%   84.34%           
=======================================
  Files          26       26           
  Lines         805      805           
=======================================
  Hits          679      679           
  Misses        126      126           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@CasperWA
CasperWA merged commit 0a48c4e into master Apr 21, 2026
16 checks passed
@CasperWA
CasperWA deleted the cwa/fix-skip-ci branch April 21, 2026 12:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants