Conversation
There was a problem hiding this comment.
Pull request overview
This is a sync PR that updates project configuration files from the source repository (mrz1836/go-broadcast) to BitcoinSchema/go-bitcoin, including version bumps for build tools, addition of benchmark comparison capabilities, and terminology standardization.
- Updated mage-x (v1.13.0 → v1.14.1) and goreleaser (v2.13.1 → v2.13.2) to latest versions
- Added benchstat tool support with new GitHub Action for benchmark comparisons
- Standardized terminology from "automation" to "tooling" and improved CVE exclusion examples
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 6 comments.
Show a summary per file
| File | Description |
|---|---|
.gitpod.yml |
Updated comments to use generic "this project" terminology instead of project-specific references |
.github/workflows/fortress-test-matrix.yml |
Added benchstat setup step to support benchmark comparison functionality |
.github/workflows/fortress-coverage.yml |
Enhanced coverage calculation with robust fallback logic and error handling for edge cases |
.github/tech-conventions/mage-x.md |
Standardized terminology from "build automation" to "build tooling/toolchain" throughout documentation |
.github/tech-conventions/README.md |
Updated MAGE-X references to use "build tooling" terminology consistently |
.github/actions/setup-benchstat/action.yml |
New composite action for installing and caching the benchstat binary across different OS platforms |
.github/.env.base |
Updated tool versions (mage-x, goreleaser), added benchstat configuration, and changed CVE example years from 2025 to 9999 |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
MAGE_X_VERSIONfromv1.13.0tov1.14.1in.github/.env.baseMAGE_X_GORELEASER_VERSIONfromv2.13.1tov2.13.2in.github/.env.baseMAGE_X_BENCHSTAT_VERSIONconfiguration variable set tov0.0.0-20251208221838-04cf7a2dca90in.github/.env.base2025to9999inNANCY_EXCLUDESandMAGE_X_CVE_EXCLUDESdocumentation comments and values.gitpod.ymlcomments from "go-bitcoin" to "this project" and "build automation" to "build tooling"Why It Was Necessary
Testing Performed
Impact / Risk