-
Commits messages must be subjective, put some time and effort now to save more later
-
Codes comments are a must, Please read these:
-
a helpful extension for comments in vscode : https://marketplace.visualstudio.com/items?itemName=cschlosser.doxdocgen
-
its always preferable to use pre-processor macros
- https://www.programiz.com/c-programming/c-preprocessor-macros
- however, always print errors "voteable" -->
-
All functions names must follow conventions and must be descriptive
-
Each part of the project is a module, a module is put in a separate repository, each repository is a submodule in a main repository for its team
-
Each team has a main repository, each is a submodule in a bigger repository for all teams
-
Write a document about your module, how to use it with other modules, and show each interface function targeted for usage in other modules
-
Add all references you used at the bottom of your repository readme file or in a separate file called references.md
-
Notifications
You must be signed in to change notification settings - Fork 0
Vehicle-Telematics-Control-Unit/.github
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
About
No description, website, or topics provided.
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published