unciaur/javabot-2023-testing

Team 2539's robot code for the 2023 season: Charged Up.

Welcome to Javabot 2023!

Team 2539's 2023 robot code is all contained within this repo (minus a couple things).

Contribution

If you are new to programming, check out our training repo: Java Training

Technical Debt

A robotics season is an intense time, so it is natural that during the process of development we will accumulate technical debt (unclean/haphazard code).

While this is unavoidable, making changes down the line becomes much easier when code is refactored and well-thought-out.

If you have extra time while writing robot code, or extra time at robot, try to consider ways that you can improve your current code so that it can be extended easily by future programmers other than yourself.

Solid code makes development and improvement much easier.

Adding Features

When adding features or refactoring the code, we recommend that you create a new branch.

The branch name should reflect the intention of the branch.

Create a new branch with (replace <my-branch> with the name of your branch):

git checkout -b <my-branch>

Merging Completed Features

Before merging, there are a few tests that should be verified.

You should test your changes on the actual robot, not just the simulator, before creating a pull request (sometimes this isn't possible or necessary, but if that's the case, you'll know it).

With that, you are ready to create a pull request, and once everything looks good, a programming team leader will approve the merge.