Skip to content

HHS-Team670/2019-Robot

Repository files navigation

2019-Robot

Code for Team 670's 2019 "Destination: Deep Space" FIRST Robotics Competition Robot "The Flex".

Repository Organization:

  • 2019-Robot: Java code and files to be deployed to run on the RoboRIO that are organized and deployed with GradleRIO
  • 2020-Robot/2019-Robot-Imported: Java code and files to be deployed on RoboRIO 2020
  • GRIP-Pipelines: GRIP Vision Pipeline files being tested
  • LED-Arduino: Arduino code to run on an arduino coprocessor to run LED lights that interface with the RoboRIO
  • PathWeaver: Contains PathWeaver files to be worked on and built into .csv files for Pathfinder to run.
  • Raspi: Code and files to be used on a raspberry pi or ODroid-XU4 coprocessor

Branching and Workflow on this Repository

Please check this document for the team's policy for committing code to GitHub!
https://docs.google.com/document/d/1vO_dtVTDw3-l0x0BabiAE5C45O6bJlQeLL1Uy9McOcQ/edit?usp=sharing
Note that you cannot commit directly to master or dev!
This project shall follow the following workflow:

The master branch is considered the stable branch of this project. It may only be updated via pull request from student developer, and then only with Shaylan's approval.

The dev branch is the main working branch. It may only be updated by pull request from uncontrolled branches.

For regular development each developer shall create a "feature branch" this is a branch named in the convention: "feature/name" or "bugfix/name". These are for new features and for bugfixes, respectively.

When work starts on a new feature, its branch will be made off of the latest version of dev, and all development will occur on the branch. When the feature is considered ready, it will be merged onto the dev branch. When merging, automatic merging, LV Merge tool merging, or simply copying and pasting of code fragments may be necessary.