[gc-stack-deploy] Run unit tests in GitHub Actions on branch push - #163
Merged
Conversation
IamJeffG
approved these changes
Jul 29, 2026
Co-authored-by: Jeffrey Gerard <IamJeffG@users.noreply.github.com>
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.
Goal
Run
gc-stack-deployunit tests in GitHub Actions on every branch push.Screenshots
Not applicable.
What I changed and why
I added a GitHub Actions workflow that runs
make -C caprover/tests test-uniton push to any branch.I also updated
caprover/tests/README.mdso the documentation matches the new CI pathHow I convinced myself this is right
Pretty straightforward but I also locally ran
What I'm not doing here
This does not add CapRover e2e,
test-e2e, ormake allto CI. It does not change the unit test suite itself.LLM use disclosure
None