Conversation
There was a problem hiding this comment.
Pull request overview
This PR synchronizes project files from the source repository (mrz1836/go-broadcast) to the target repository (BitcoinSchema/go-bitcoin). The sync includes version updates for Go tooling, a new mage-x version, and introduces two composite actions for improved CI/CD workflow management with resource-saving failure handling.
Changes:
- Updated Go and mage-x versions in environment configuration
- Added workflow cancellation action to stop unnecessary parallel jobs when critical failures occur
- Enhanced artifact download action with better error handling and API resilience
- Integrated new actions across multiple workflow files with appropriate permission updates
Reviewed changes
Copilot reviewed 11 out of 11 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
.github/.env.base |
Updated GOVULNCHECK_GO_VERSION to 1.25.6 and MAGE_X_VERSION to v1.18.0 |
.github/workflows/fortress.yml |
Updated version/date, repository URL, added actions:write permissions, refined completion report conditions |
.github/workflows/fortress-test-suite.yml |
Changed permissions from actions:read to actions:write for test workflows |
.github/workflows/fortress-test-matrix.yml |
Added actions:write permission and integrated workflow cancellation on failure |
.github/workflows/fortress-test-fuzz.yml |
Added actions:write permission and integrated workflow cancellation on failure |
.github/workflows/fortress-security-scans.yml |
Added actions:write permissions and workflow cancellation for all security scan jobs |
.github/workflows/fortress-pre-commit.yml |
Added actions:write permission and workflow cancellation on failure |
.github/workflows/fortress-code-quality.yml |
Added actions:write permissions and workflow cancellation for quality check jobs |
.github/workflows/fortress-completion-report.yml |
Made multiple inputs optional with default values for better error handling |
.github/actions/cancel-workflow-on-failure/action.yml |
New composite action for cancelling workflows on critical failures with comprehensive error handling |
.github/actions/download-artifact-resilient/action.yml |
Enhanced artifact download with improved API error handling and validation |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Member
Author
|
LGTM! |
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.
What Changed
GOVULNCHECK_GO_VERSIONfrom1.25.5to1.25.6in.github/.env.baseMAGE_X_VERSIONfromv1.17.4tov1.18.0in.github/.env.base.github/actions/cancel-workflow-on-failure/action.ymlthat provides workflow cancellation capability when critical jobs fail.github/actions/download-artifact-resilient/action.ymlfor resilient artifact downloadsWhy It Was Necessary
Testing Performed
.env.basewill be validated by existing CI workflows that consume these variablesactions: write) are documented in the new action to ensure proper authorizationImpact / Risk