From f9f6fe57dac25e83ff5d185b5fb9c999e1a27428 Mon Sep 17 00:00:00 2001 From: sciencewhiz Date: Sun, 16 Jun 2024 07:26:59 -0700 Subject: [PATCH 1/2] Pin Ramsete example links to last tag Removed in main. Issue #2651 exists for updating --- .../trajectory-tutorial/trajectory-tutorial-overview.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/docs/software/pathplanning/trajectory-tutorial/trajectory-tutorial-overview.rst b/source/docs/software/pathplanning/trajectory-tutorial/trajectory-tutorial-overview.rst index 7ba2ecfb6f..310ed40822 100644 --- a/source/docs/software/pathplanning/trajectory-tutorial/trajectory-tutorial-overview.rst +++ b/source/docs/software/pathplanning/trajectory-tutorial/trajectory-tutorial-overview.rst @@ -18,7 +18,7 @@ The goal of this tutorial is to provide "end-to-end" instruction on implementing This tutorial is intended to be approachable for teams without a great deal of programming expertise. While the WPILib library offers significant flexibility in the manner in which its trajectory-following features are implemented, closely following the implementation outlined in this tutorial should provide teams with a relatively-simple, clean, and repeatable solution for autonomous movement. -The full robot code for this tutorial can be found in the RamseteCommand Example Project (`Java `__, `C++ `__). +The full robot code for this tutorial can be found in the RamseteCommand Example Project (`Java `__, `C++ `__). Why Trajectory Following? ------------------------- From 73905f703ee7739b635da78efec8bb4e23e09fa0 Mon Sep 17 00:00:00 2001 From: sciencewhiz Date: Mon, 17 Jun 2024 19:54:08 -0700 Subject: [PATCH 2/2] Add RLI ignores --- .github/workflows/inspector.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/inspector.json b/.github/workflows/inspector.json index 37473c667b..832a7633d6 100644 --- a/.github/workflows/inspector.json +++ b/.github/workflows/inspector.json @@ -26,5 +26,5 @@ "latestVersion":"6a5b6352807a8759bd0f012e57695c47f7ef7324" } ], - "ignoredFiles": ["source/docs/software/commandbased/command-scheduler.rst", "source/docs/software/hardware-apis/pneumatics/pressure.rst", "source/docs/software/hardware-apis/pneumatics/solenoids.rst", "source/docs/software/advanced-controls/state-space/state-space-pose-estimators.rst", "source/docs/software/commandbased/pid-subsystems-commands.rst", "source/docs/software/commandbased/profilepid-subsystems-commands.rst", "source/docs/software/commandbased/subsystems.rst", "source/docs/software/telemetry/writing-sendable-classes.rst"] + "ignoredFiles": ["source/docs/software/commandbased/command-scheduler.rst", "source/docs/software/hardware-apis/pneumatics/pressure.rst", "source/docs/software/hardware-apis/pneumatics/solenoids.rst", "source/docs/software/advanced-controls/state-space/state-space-pose-estimators.rst", "source/docs/software/commandbased/pid-subsystems-commands.rst", "source/docs/software/commandbased/profilepid-subsystems-commands.rst", "source/docs/software/commandbased/subsystems.rst", "source/docs/software/telemetry/writing-sendable-classes.rst", "source/docs/software/advanced-controls/trajectories/troubleshooting.rst", "source/docs/software/hardware-apis/motors/wpi-drive-classes.rst", "source/docs/software/pathplanning/trajectory-tutorial/creating-drive-subsystem.rst", "source/docs/software/pathplanning/trajectory-tutorial/creating-following-trajectory.rst", "source/docs/software/pathplanning/trajectory-tutorial/entering-constants.rst"] }