Conversation
Synced with golang std http fs_test.go https://github.com/golang/go/blob/456a90aa1618a6c3aa49ecba46969128e2bfa26f/src/net/http/fs_test.go#L607 See upstream comment why this is needed. We should probably rebase devd fileserver.* on latest golang fs.*
This commit changes the default virtual hosting domain from devd.io to localhost (and *.localhost). Resolves cortesi#128
Replace devd.io with localhost for local routing
…tEncoding Fix failing TestServeFileWithContentEncoding
Update readme go install process
…being-set Use HTTPS scheme when specifying cert file
go get -u && go mod tidy
Remove broken Travis CI configuration (.travis.yml) Add GitHub Actions workflow for testing on ubuntu, macos, and windows Strictly test on Go 1.25.x to match the go.mod directive Include gofmt, go vet, and go install to ensure build integrity
chebread
changed the title
chebread
changed the title
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
4 participants
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.
I have updated the CI pipeline to use GitHub Actions, replacing the broken Travis CI and AppVeyor setups.
Changes
Technical Implementation Details
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true. This prepares the repository for the upcoming Node 20 EOL (April 2026) and ensures the CI remains functional and secure without deprecation warnings.workflow_dispatchto allow manual trigger of the CI from the Actions tab, providing better control for debugging or maintenance.gofmt: Ensures all contributions follow the standard Go style, reducing reviewer burden.go vet: Catch common logical errors at the CI stage.go run ./cmd/devd --helpto verify the final binary's execution integrity across all platforms.Note on AppVeyor
I found that AppVeyor was likely configured via the Web UI rather than a .appveyor.yml file, as no such file existed in the root. Therefore, I could not "delete" its configuration via git. Once this PR is merged, the repository owner should manually disable the AppVeyor project in its admin dashboard to avoid redundant (and failing) builds.
Verification
I have verified this entire workflow on my fork, and all three OS environments passed the build and test suites successfully.