ZekiLiu opened a new pull request, #829:
URL: https://github.com/apache/incubator-graphar/pull/829

   Introduce a minimal Go module and CI workflow (Go 1.21) for the upcoming Go 
SDK.
   
   <!--
   Thanks for contributing to GraphAr.
   If this is your first pull request you can find detailed information on 
[CONTRIBUTING.md](https://github.com/apache/graphar/blob/main/CONTRIBUTING.md)
   
   The Apache GraphAr (incubating) community has restrictions on the naming of 
pr title. You can find instructions in
   
[CONTRIBUTING.md](https://github.com/apache/graphar/blob/main/CONTRIBUTING.md#title)
 too.
   -->
   
   ### Reason for this PR
   <!-- 
   Why are you proposing this change? If this is already tracked in an issue, 
please link to the issue here.
   Explaining clearly why this change is beneficial is important for the 
reviewers to understand the context.
   -->
   This PR bootstraps the initial Go SDK skeleton under `go/` and sets up CI to 
run Go tests.
   It is intended to provide a minimal, reviewable baseline so the community 
can iterate on the Go SDK design and implementation incrementally.  #828 
   
   ### What changes are included in this PR?
   <!-- 
   There is no need to duplicate the description in the issue here but it is 
sometimes worth providing a summary of the individual changes in this PR.
   -->
   - Add a Go module under `go/` (`go/go.mod`, Go 1.21).
   - Add a minimal SDK entrypoint (`graphar.Client` and `graphar.NewClient()`).
   - Add a minimal unit test to ensure the module is buildable and testable.
   - Add a GitHub Actions workflow (`.github/workflows/go.yml`) to run `go 
test` on changes in `go/**`.
   - Add `go/Makefile` with `make test` for a consistent developer workflow 
(aligned with other language subprojects).
   
   ### Are these changes tested?
   <!--
   We typically require tests for all PRs in order to:
   1. Prevent the code from being accidentally broken by subsequent changes
   2. Serve as another way to document the expected behavior of the code
   
   If tests are not included in your PR, please explain why (for example, are 
they covered by existing tests)?
   -->
   Yes.
   - Unit test: `go test ./...` (executed in CI via `.github/workflows/go.yml`).
   - The CI workflow is path-filtered to run when Go-related files change.
   
   ### Are there any user-facing changes?
   <!--
   If there are user-facing changes then we may require documentation to be 
updated before approving the PR.
   -->
   No. This PR only introduces the initial project skeleton and CI for the Go 
SDK; it does not implement GraphAr format reading/writing yet.
   
   <!--
   If there are any breaking changes to public APIs, please uncomment the line 
below and explain which changes are breaking.
   -->
   <!-- **BREAKING CHANGE: <description>** -->
   
   <!--
   Please uncomment the line below (and provide explanation) if the changes fix 
either
   (a) a security vulnerability,
   (b) a bug that caused incorrect or invalid data to be produced, or
   (c) a bug that causes a crash (even when the API contract is upheld). 
   We use this to highlight fixes to issues that may affect users without their 
knowledge. For this reason, fixing bugs that cause errors don't count, since 
those are usually obvious.
   -->
   <!-- **Critical Fix: <description>** -->


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to