-
If you estimate a change will not take you more than one day, it is okay to edit the code without making a new branch Just make sure that people are aware of this and push your changes when you finish
-
If you are planning a significant, multi-day project, it is best to create a new branch then merge it in later. The branch name should be a short overview of what you plan to do. Send a message in channel before merging so everyone is aware of large changes.
-
If you are creating new scripts, place them in a folder that has a descriptive name. This is so that if a project needs multiple code files, they can still stay organized.
-
Check the files you have modified before making a commit. If you see a change to a file that you don't remember making, please check it and do not commit it if it was unintentional
-
Notifications
You must be signed in to change notification settings - Fork 0
Purdue-Space-Program/PSPL_R4_Avionics_Sizing
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
About
Spreadsheets and Code for Avionics Rocket 4
Resources
Stars
Watchers
Forks
Releases
No releases published
Packages 0
No packages published