-
Notifications
You must be signed in to change notification settings - Fork 0
Git Flow
Octavia Togami edited this page Feb 24, 2022
·
3 revisions
This page describes our Git and GitHub policy.
Here's how it works:
-
masteris the main branch. All code onmasterMUST compile AND pass tests.mastermay not be pushed to directly or have its history rewritten. - Feature branches
- Feature branches are named as follows:
feature/<the-feature-you-are-adding>. Examples from our previous project:feature/DOCUMENT-EVERYTHING,feature/lidar, etc. - Feature branches are usually worked on by one or two developers. There's not many guidelines for them other than that.
- When a feature branch is complete, propose it as a PR on GitHub. See this for more information.
- Feature branches are named as follows:
- PRs
- One developer MUST approve the PR before it is merged. This is enforced by GitHub.
- Tutorials
- Getting the JDK
- Getting IntelliJ
- Learn Java
- Coding Your First Robot
- Basic Drive Systems
- Command-Based Programming
- 5818-lib
- Dependency Injection
- Formatting Guide
- Command Line Guide
- Quick References
- WPILib Documentation
- Git Book (External Resource)
- Robot Documentation
- Rogue Cephalopod (2017)