Repository Conduct Guide

The following is a set of rules for that each member of the team must follow when participating in the development of the Satellite's code base. In addition this will also include the life cycle of the repository and action plans for posable events.

Code Base Best Praticies

Pre Commit Check

Each member of the team must complete a pre commit check before any changes are pushed.

These include

• Code must have correct and meaning comments
• Variable names must have unique and meaningful names
• Variables, functions, types, structs, and typedefs must follow the snake_case naming convention
• Ensure that wiki documentation is updated to reflect the changes made