Fix CI workflows to trigger on Go file changes #44
+845
−106
Conversation
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
So we can pull from any OCI registry, add authentication, etc. Add docker-style progress bars and resumable downloads to OCI pulls Update documentation with progress bars and resumable downloads info Signed-off-by: Eric Curtin <[email protected]>
Co-authored-by: ericcurtin <[email protected]>
Copilot
AI
changed the title
[WIP] Fix CI GitHub Actions builds in pull request
Fix CI workflows to trigger on Go file changes
Oct 19, 2025
Copilot finished work on behalf of
ericcurtin
October 19, 2025 17:53
ericcurtin
force-pushed
the
integrate-go-containerregistry-library
branch
8 times, most recently
from
e4b192d to
2935963
Compare
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.
Problem
The repository includes Go code for OCI registry integration in the
oci-go/directory (added in the base commit), but the CI workflow path filters only included C/C++, Swift, Metal, and other source files. This meant that changes to Go files (*.go,go.mod,go.sum) would not trigger CI builds, potentially allowing untested Go code changes to be merged.Solution
Added Go file patterns to the path filters in the following workflows:
build.yml- Main CI build workflow (push and pull_request triggers)build-amd.yml- AMD-specific build workflow (push trigger)release.yml- Release workflow (push trigger)server.yml- Server tests workflow (push and pull_request triggers)Each workflow now includes:
**/*.go- Go source files**/go.mod- Go module definition**/go.sum- Go module checksumsVerification
oci-go/builds without errorsNow when Go files are modified, the appropriate CI workflows will trigger and validate the changes, ensuring the same level of testing coverage as other source files in the repository.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.