-
Notifications
You must be signed in to change notification settings - Fork 2
Github code format
We are using default code format style of clang-format, in future when Boost.uBLAS agrees to use one code format style, the code format style file named .clang-format
will be added in the root of the project and our CI will be formatting and checking based on that style file.
The following codes are only affected by code formatting:
examples/tensor/*.cpp
tests/tensor/*.cpp
include/numeric/ublas/tensor/*.hpp (any hpp inside tensor directory)
include/numeric/ublas/tensor/*/*.hpp (any subdirectory inside tensor with hpp extension)
If you want to cover more areas with code formatting, please add the location to that directory in the file named check_format.yml
inside of the .github/workflows
directory.
When I added the CI workflow for the Code format check, the code was not correctly formatted to any one single style. The CI checked it and found that the code format was not well, so it failed. You can check the failure here
NOTE: CI will fail if code is not correctly formatted, both for Push and PR
I thank our mentor Cem for his constant support and help in achieving our goals. We always find him helpful and he was always easy to reach for help or discussion regarding the work. We would also like to thank Google for the Google Summer of Code Programme, without which all these wouldn't be possible. Lastly, we express our gratitude to our parents for helping and providing us with all resources to carrying out our work nicely from our homes.
- Project Proposal
- Milestones and Tasks
- Implementation
- cpp20
- github-actions
- features/tidy
- features/format
- features/cmake
- Documentation
- Pull Requests
- Future Work