Repository navigation
fix(ci): use signed squash merges with ci-github-publish 1.0.3 - #559
Merged
Merged
Conversation
Contributor
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
neilime
force-pushed
the
fix/ci-publish-squash-merges
branch
from
October 29, 2026 16:58
72507a8 to
c279b5f
Compare
Contributor
|
Code Coverage Report Coverage ResultsCoverage
Overall: 100.00% 🟢 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #559 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 3 3
=========================================
Hits 3 3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
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.
Documentation updates fail when the release workflow tries to rebase a documentation PR into a branch requiring signed commits. GitHub cannot sign those rebase merges, as shown in the failed CI job.
Upgrade all
ci-github-publishworkflow and action references from1.0.2to1.0.3, pinned toea6682de88070c254dac619a6623a242a6d57cd3, and selectmerge-method: squashfor documentation updates. Version1.0.3includes the merge-method input from hoverkraft-tech/ci-github-publish#492. Update the release guide examples and links to the same version.Squash merging is enabled in the repository settings. Existing signature and review requirements still apply.
Validation completed:
make lintfor the three workflows and release guide.1.0.3input contracts, including squash forwarding.git diff --check.