feat(ci): add basic workflow and CMake entrypoint.#17
Conversation
|
Thank you for your interest in and contribution to paimon-cpp. We are currently in the process of migrating the codebase, and the CI pipeline will be improved step by step afterward. Merging new functionality at this stage may add extra complexity to the remaining migration work. You are very welcome to contribute to paimon-cpp again once the migration is completed. Thanks again for your support and understanding! |
@zjw1111 Thank you for the clarification and feedback! I understand that the project is currently undergoing codebase migration, and merging new functionality at this stage may add extra complexity to the migration work. I will keep these changes for now and revisit them after the migration is completed and the CI pipeline becomes more stable, adapting them to the new code structure before contributing again. Thanks again for your maintenance efforts, and I look forward to continuing to contribute to paimon-cpp in the future. |
|
@zjw1111 I will close the related PRs for now. Is there anything I can help with during the current migration stage? |
Thanks for asking! I’ll reach out if anything comes up where coordination or review would be helpful. |
|
BTW, our current main repository is still at https://github.com/alibaba/paimon-cpp. Since the migration to Apache may take some time, if you would like to try things out quickly or contribute new features, it might be easier to work with the original repository for now. We will continue to upstream all changes to Apache incrementally. Thanks again for your interest! |
Purpose
Linked issue: close #16
Add a basic GitHub Actions CI workflow for pull request checks.
This PR introduces:
pre-commitjob to run repository hygiene checks withpre-commit run --all-files.cmakejob to verify that the project can be configured and built with CMake.CMakeLists.txtas the initial CMake entrypoint.This is intended as the first CI step for the repository. Full unit test execution can be added incrementally after the CMake build/test targets and dependency setup become more complete.
Tests
Verified locally
API and Format
No.
Documentation
No user-facing documentation is added.
Generative AI tooling