Project files

Git/GitHub Version Control and Collaboration Exercise (10 points)

Problem Description

Use Git to manage the entire project, preserving the real development history from CAD, URDF, simulation, controllers, Linux, MCU, to CAN. Establish main, develop, and feature branches divided by modules; when multiple developers are involved, use feature/<name>/<module>, and merge via Pull Request while retaining review records.

Commits must describe actual work, for example feat: add wheelleg urdf, fix: correct joint axis, test: validate can frame parser. Meaningless messages like update, aaa, 111, final are prohibited. It is recommended to use milestone tags from v0.1.0 to v1.0.0; specific requirements are detailed in ../docs/development_log.md.

Deliverables

GitHub repository, traceable commit history, branches, tags, pull requests, releases, and records that prove the contribution scope of each member.

Suggested Submission of Completed Work

Testers and developers are encouraged to complete their own simulations or physical builds based on this repository's architecture and submit their results to other branches of this repository. It is recommended to use branches named submission/<name>/<version> or submission/<team>/<version>, and create a Pull Request targeting develop after preserving the full commit history. Submission content should include build/flash steps, hardware version, test logs, demonstration videos, CAD and URDF consistency documentation, CNC/machining preview screenshots, and known issues. Directly overwriting main/develop or using one-time final commits is prohibited. If you lack write permissions, you may first Fork the repository and then submit via Pull Request.

Scoring

Severe Deductions

If you upload all content at once, have a module with only an Add everything history, plagiarize others' code, or lack corresponding branch/PR evidence, your score will be based solely on verifiable actual contributions.