ci: add PR checks for app, frontend, and DocReader - #2416
Merged
Conversation
lyingbug
marked this pull request as ready for review
July 30, 2026 04:36
Start the DocReader gRPC server in the DocReader workflow, skip client integration tests when the server is unavailable, exclude docreader packages from the App workflow test scope, and trigger DocReader checks on go.mod/go.sum changes.
Use setup-go v6 default go.mod cache key instead of go.sum, warm the module cache with an explicit go mod download step, and scope vet to the same package set as tests.
Compare base...head for pull_request events instead of the merge commit so unrelated main-branch files are not checked. Also gofmt kb_access_test.go, which was unformatted on main.
lyingbug
force-pushed
the
agent/add-core-pr-ci
branch
3 times, most recently
from
July 30, 2026 06:12
7a435a4 to
7adb465
Compare
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
1 participant
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
Why
Changes under these three core paths did not have dedicated pull-request checks, so regressions could be merged without exercising the corresponding build and test suites.
Impact
Each workflow is scoped to its relevant paths to avoid unnecessary CI work. Existing runtime behavior is unchanged; supporting fixes align public terminology, stabilize test-only SSRF configuration, and skip DocReader tests whose optional fixture files are absent.
Validation