Swap out rebelib (#14)

Author: TNilCode

.github/workflows/build.yml

@@ -11,8 +11,6 @@ jobs:
     steps:
       - name: Checkout repository
         uses: actions/checkout@v4
-        with:
-            submodules: 'recursive'
       - name: Grant execute permission
         run: chmod +x gradlew
       - name: Build robot code

.github/workflows/check-format.yml

@@ -13,8 +13,6 @@ jobs:
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
-        with:
-            submodules: 'recursive'
 
       - name: Set up JDK
         uses: actions/setup-java@v4

.github/workflows/javadoc.yml

@@ -14,8 +14,6 @@ jobs:
     steps:
       - name: Checkout repository
         uses: actions/checkout@v4
-        with:
-            submodules: 'recursive'
 
       - name: Set up JDK
         uses: actions/setup-java@v4

.github/workflows/lint.yml

@@ -16,8 +16,6 @@ jobs:
     steps:
       - name: Checkout code
         uses: actions/checkout@v4
-        with:
-            submodules: 'recursive'
 
       - name: Set up JDK
         uses: actions/setup-java@v4

.github/workflows/submodule-check.yml

@@ -15,7 +15,7 @@
 Open git bash or your sh of choice and run the following commands:
 
 ```sh
-git clone --recurse-submodules --remote-submodules <the URL of this repository>.git
+git clone <the URL of this repository>.git
 cd <the name of the repository>
 ./scripts/install-hooks.sh
 ```
@@ -26,11 +26,9 @@ Then open the root directory of the repository in WPILib VSCode
 
 All code changes should happen on a branch, and then a PR should be opened and reviewed by multiple senior members or leads before being merged. Commits should contain a single set of related changes, and commit names should be descriptive of their contents. Err on the side of granularity when committing, as it's easier to clean up later. Push whenever code is in a reasonable state and prior to leaving. Pull often, and keep up with changes on `main` and other branches. Reviews should be thorough, lest you tear your hair out debugging later (do *not* LGTM). No code should go into `main` that hasn't been simulated thoroughly and/or tested on a robot, and no incomplete or in-progress code should be merged. All code should be formatted on build, and should follow WPILib command-based programming best practices.
 
-## RebeLib
+## Lib Directory
 
-RebeLib exists within this project as a git submodule, managed by a set of scripts. To make changes to RebeLib, change into the `src/main/java/frc/RebeLib` directory and branch, commit, and push your changes. Once your RebeLib changes are pushed to a branch, you can commit and push to this project. A Github Action requires that RebeLib be set to the newest `main` before merging, so any PRs to RebeLib must be merged first. Once RebeLib is merged, pull it from this project and commit the new hash to make the Action pass so that you can merge.
-
-Any code that is season-agnostic should live in RebeLib, and should be maintained.
+The `lib` directory (`rebellion-template/src/main/java/frc/lib`) contains reusable files and utilities. This should be copy-paste-able between robot projects (relying on nothing outside the `lib` directory) and should be self contained. These files can be moved, added, or removed as needed.
 
 ## Github Pages Javadoc
 

.gitmodules

@@ -1,7 +1,5 @@
 #!/bin/sh
 
-./scripts/update-submodule.sh src/main/java/frc/RebeLib
-
 ./scripts/check-gradlew.sh
 if [ $? -ne 0 ]; then
   exit 1