[Sync] Update project files from source repository (f06ac07)

[mrz1836]

What Changed

• Updated 7 individual file(s) to synchronize with the source repository
• Synchronized 2 file(s) from directory mappings
• Applied file transformations and updates based on sync configuration
• Brought target repository in line with source repository state at commit 426f46d

Directory Synchronization Details

The following directories were synchronized:

.github/workflows → .github/workflows

• Files synced: 2
• Files examined: 24
• Files excluded: 0
• Processing time: 4225ms

.github/actions → .github/actions

• Files synced: 0
• Files examined: 16
• Files excluded: 0
• Processing time: 2985ms

.vscode → .vscode

• Files synced: 0
• Files examined: 4
• Files excluded: 0
• Processing time: 1887ms

.github/tech-conventions → .github/tech-conventions

• Files synced: 0
• Files examined: 15
• Files excluded: 0
• Processing time: 3088ms

.github/ISSUE_TEMPLATE → .github/ISSUE_TEMPLATE

• Files synced: 0
• Files examined: 3
• Files excluded: 0
• Processing time: 1096ms

Performance Metrics

• Files processed: 84 (9 changed, 0 deleted, 75 skipped)
• Files attempted to change: 9 (go-broadcast processing)
• File processing time: 7354ms

Why It Was Necessary

This synchronization ensures the target repository stays up-to-date with the latest changes from the configured source repository. The sync operation identifies and applies only the necessary file changes while maintaining consistency across repositories.

Testing Performed

• Validated sync configuration and file mappings
• Verified file transformations applied correctly
• Confirmed no unintended changes were introduced
• All automated checks and linters passed

Impact / Risk

• Low Risk: Standard sync operation with established patterns
• No Breaking Changes: File updates maintain backward compatibility
• Performance: No impact on application performance
• Dependencies: No dependency changes included in this sync

[Copilot]

Pull Request Overview

This pull request synchronizes configuration and build files from the source repository (mrz1836/go-broadcast) to the target repository (bsv-blockchain/go-tx-map), updating the project to use the magex build system and modernizing various configuration files.

Key changes include:

• Migration from traditional make-based builds to magex build system
• Updates to GitHub Actions workflow configurations with newer action versions
• Enhanced development environment configurations for Gitpod and DevContainer

Reviewed Changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
codecov.yml	Added flag management configuration and updated ignore paths
.goreleaser.yml	Migrated from make to magex, added archive and checksum configurations
.gitpod.yml	Complete rewrite to use magex with improved developer onboarding
.github/workflows/scorecard.yml	Updated CodeQL action version hash
.github/workflows/codeql-analysis.yml	Updated CodeQL action version hashes across multiple steps
.github/.env.base	Updated MAGE_X_VERSION from v1.7.2 to v1.7.5
.dockerignore	Reorganized and added new project-specific ignore patterns
.devcontainer.json	Updated VS Code settings and migrated commands to magex
.cursorrules	Updated development commands to use magex instead of make

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting

• @codex fix this CI failure
• @codex address that feedback