Conversation
WalkthroughThis pull request inserts a "Last tested" blockquote line into 22 documentation files across workspace and docker-module docs. Changes are text-only additions near introductions or headers; no code, logic, or public API was modified. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 11
🤖 Fix all issues with AI agents
In `@docs/delto-gripper-ws/index.md`:
- Line 14: Replace the placeholder line "Last tested on TODO." with the actual
commit reference and author info used elsewhere in the docs: insert the full
commit hash and the author name/email in the same format as other entries (e.g.,
"Last tested on <commit-hash> by <Author Name>"), ensuring you copy the exact
commit hash from the repository history for the tested state and replace the
TODO text accordingly.
In `@docs/docker-modules/cartographer.md`:
- Around line 7-8: Replace the placeholder line "Last tested on TODO." in
docs/docker-modules/cartographer.md with a concrete value or remove it: either
insert the actual commit hash or date/build tag used for the last successful
test (matching the style used in docs/stretch3-ws/index.md), or reword to a
non-specific statement (e.g., "Last tested on [date]") and remove the TODO
before merging so the published doc contains no visible TODO text.
In `@docs/docker-modules/cuda-toolkit.md`:
- Line 7: Replace the placeholder text "Last tested on TODO." with a concrete
identifier such as a commit hash (e.g., abc1234), a full date (e.g.,
2026-02-05), or both so the note is actionable; update the line containing "Last
tested on TODO." to read something like "Last tested on <commit-hash>
(<YYYY-MM-DD>)" or your chosen format.
In `@docs/docker-modules/isaac-lab.md`:
- Line 7: Replace the placeholder "TODO" in the "Last tested on TODO." line with
a concrete identifier of the tested state (either a full commit hash like "Last
tested on commit abc1234..." or an exact date like "Last tested on 2025-02-05");
ensure the entry points to the specific commit or tag used to verify the docs so
readers can reproduce the exact documented state.
In `@docs/docker-modules/isaac-ros.md`:
- Line 9: Replace the placeholder "Last tested on TODO." with the concrete
commit reference in the same format used elsewhere (commit hash and author),
e.g. "Last tested on <commit-hash> by <author-name>." Ensure the commit hash is
the exact tested commit and the author matches the repo attribution formatting
used in other docs.
In `@docs/h1-ws/index.md`:
- Line 14: Replace the placeholder text "Last tested on TODO." with a concrete
commit reference and author so the docs are actionable; update the line
containing "Last tested on TODO." to something like "Last tested on
<commit-hash> by <author-name>" (use the full commit SHA and the
committer/author name) and ensure the commit hash is accurate for the tested
state referenced in the rest of the doc.
In `@docs/kobuki-ws/index.md`:
- Line 14: Replace the placeholder "TODO" in the "Last tested on TODO." line
with a concrete commit hash or ISO date so users can reproduce the tested tree;
update the sentence to read e.g. "Last tested on <commit-hash>" or "Last tested
on YYYY-MM-DD" (use the commit SHA from the repo at test time or the exact date
of testing) and ensure the commit hash is full/short SHA consistently used
across docs.
In `@docs/orbslam3-ws/index.md`:
- Line 12: Replace the placeholder "Last tested on TODO." in
docs/orbslam3-ws/index.md with a concrete Git commit hash (and optionally a
date) that was used to verify the PR; locate the exact string "Last tested on
TODO." in the file and update it to something like "Last tested on <commit-hash>
(<YYYY-MM-DD>)" so the documentation records the specific tested revision.
In `@docs/ros1-bridge-ws/index.md`:
- Line 19: Replace the placeholder "Last tested on TODO." in the docs header
with a concrete identifier: update the exact line containing "Last tested on
TODO." to include the actual last-tested git commit hash (e.g. abc1234) and
optionally the date (e.g. 2026-02-05) so it reads like "Last tested on abc1234
(2026-02-05)"; ensure you use the real commit used for verification and keep the
wording/format consistent with other docs.
In `@docs/template-ws/index.md`:
- Line 14: Replace the placeholder "TODO" in the "Last tested on TODO." line
with a concrete identifier: the commit SHA (preferred) and optionally the date
used for testing (e.g., "Last tested on commit abc1234 (2026-02-05)"); update
the text exactly where the phrase appears so it reads with the chosen commit
hash and/or date to make the test reference reproducible.
In `@docs/vlp-ws/index.md`:
- Line 12: Replace the placeholder "Last tested on TODO." with a concrete commit
reference: include the short or full commit hash and the author (e.g., "Last
tested on <commit-hash> by <author-name>") and optionally the commit date;
update the line in docs/vlp-ws/index.md so the note reads a specific, actionable
reference rather than TODO.
🧹 Nitpick comments (1)
docs/docker-modules/codex.md (1)
7-7: Consider adding the test date next to the commit.Including an explicit date (e.g., “Last tested on 2026‑02‑05, commit …”) makes troubleshooting easier when users compare instructions against time-bound dependency changes.
|
|
||
| This repository will help you configure the environment for Delto Gripper quickly. | ||
|
|
||
| > Last tested on TODO. |
There was a problem hiding this comment.
Replace the TODO with a concrete commit reference.
User-facing docs shouldn’t ship with a placeholder; please include the tested commit hash and author (matching the format used elsewhere).
🤖 Prompt for AI Agents
In `@docs/delto-gripper-ws/index.md` at line 14, Replace the placeholder line
"Last tested on TODO." with the actual commit reference and author info used
elsewhere in the docs: insert the full commit hash and the author name/email in
the same format as other entries (e.g., "Last tested on <commit-hash> by <Author
Name>"), ensuring you copy the exact commit hash from the repository history for
the tested state and replace the TODO text accordingly.
|
|
||
| CUDA Toolkit 12.6 Deb Install. (Not installed by default.) | ||
|
|
||
| > Last tested on TODO. |
There was a problem hiding this comment.
Replace “TODO” with a concrete commit or date.
Please fill in the actual last tested commit so the note is actionable.
🤖 Prompt for AI Agents
In `@docs/docker-modules/cuda-toolkit.md` at line 7, Replace the placeholder text
"Last tested on TODO." with a concrete identifier such as a commit hash (e.g.,
abc1234), a full date (e.g., 2026-02-05), or both so the note is actionable;
update the line containing "Last tested on TODO." to read something like "Last
tested on <commit-hash> (<YYYY-MM-DD>)" or your chosen format.
|
|
||
| Isaac Lab 2.1.0 Git Install. | ||
|
|
||
| > Last tested on TODO. |
There was a problem hiding this comment.
Replace “TODO” with a concrete commit or date.
This should point to the tested commit so readers can reproduce the doc state.
🤖 Prompt for AI Agents
In `@docs/docker-modules/isaac-lab.md` at line 7, Replace the placeholder "TODO"
in the "Last tested on TODO." line with a concrete identifier of the tested
state (either a full commit hash like "Last tested on commit abc1234..." or an
exact date like "Last tested on 2025-02-05"); ensure the entry points to the
specific commit or tag used to verify the docs so readers can reproduce the
exact documented state.
|
|
||
| Isaac ROS 3.2. (Not installed by default.) | ||
|
|
||
| > Last tested on TODO. |
There was a problem hiding this comment.
Replace the TODO with a concrete commit reference.
Please provide the tested commit hash and author, matching the format used in other docs.
🤖 Prompt for AI Agents
In `@docs/docker-modules/isaac-ros.md` at line 9, Replace the placeholder "Last
tested on TODO." with the concrete commit reference in the same format used
elsewhere (commit hash and author), e.g. "Last tested on <commit-hash> by
<author-name>." Ensure the commit hash is the exact tested commit and the author
matches the repo attribution formatting used in other docs.
|
|
||
| This repository facilitates the quick configuration of the simulation environment and real robot driver for Kobuki. | ||
|
|
||
| > Last tested on TODO. |
There was a problem hiding this comment.
Replace “TODO” with a concrete commit or date.
Please fill in the tested commit so users can reset their tree accurately.
🤖 Prompt for AI Agents
In `@docs/kobuki-ws/index.md` at line 14, Replace the placeholder "TODO" in the
"Last tested on TODO." line with a concrete commit hash or ISO date so users can
reproduce the tested tree; update the sentence to read e.g. "Last tested on
<commit-hash>" or "Last tested on YYYY-MM-DD" (use the commit SHA from the repo
at test time or the exact date of testing) and ensure the commit hash is
full/short SHA consistently used across docs.
|  | ||
|  | ||
|
|
||
| > Last tested on TODO. |
There was a problem hiding this comment.
Replace “TODO” with a concrete commit or date.
The PR objective is to record the last tested commit; leaving a TODO defeats that purpose. Please fill in a specific commit hash (and optionally a date).
🤖 Prompt for AI Agents
In `@docs/orbslam3-ws/index.md` at line 12, Replace the placeholder "Last tested
on TODO." in docs/orbslam3-ws/index.md with a concrete Git commit hash (and
optionally a date) that was used to verify the PR; locate the exact string "Last
tested on TODO." in the file and update it to something like "Last tested on
<commit-hash> (<YYYY-MM-DD>)" so the documentation records the specific tested
revision.
|
|
||
| This workspace is utilized to create a bridge between ROS1 and ROS2-humble. | ||
|
|
||
| > Last tested on TODO. |
There was a problem hiding this comment.
Replace “TODO” with a concrete commit or date.
Please provide the actual last tested commit (and optionally the date) so users can reset their tree as intended.
🤖 Prompt for AI Agents
In `@docs/ros1-bridge-ws/index.md` at line 19, Replace the placeholder "Last
tested on TODO." in the docs header with a concrete identifier: update the exact
line containing "Last tested on TODO." to include the actual last-tested git
commit hash (e.g. abc1234) and optionally the date (e.g. 2026-02-05) so it reads
like "Last tested on abc1234 (2026-02-05)"; ensure you use the real commit used
for verification and keep the wording/format consistent with other docs.
|
|
||
| This template will help you set up a ROS-Humble environment quickly. | ||
|
|
||
| > Last tested on TODO. |
There was a problem hiding this comment.
Replace “TODO” with a concrete commit or date.
To make debugging reproducible, this should reference the tested commit hash (and optionally the date).
🤖 Prompt for AI Agents
In `@docs/template-ws/index.md` at line 14, Replace the placeholder "TODO" in the
"Last tested on TODO." line with a concrete identifier: the commit SHA
(preferred) and optionally the date used for testing (e.g., "Last tested on
commit abc1234 (2026-02-05)"); update the text exactly where the phrase appears
so it reads with the chosen commit hash and/or date to make the test reference
reproducible.
|  | ||
|  | ||
|
|
||
| > Last tested on TODO. |
There was a problem hiding this comment.
Replace the TODO with a concrete commit reference.
Please include the tested commit hash and author to keep the note actionable.
🤖 Prompt for AI Agents
In `@docs/vlp-ws/index.md` at line 12, Replace the placeholder "Last tested on
TODO." with a concrete commit reference: include the short or full commit hash
and the author (e.g., "Last tested on <commit-hash> by <author-name>") and
optionally the commit date; update the line in docs/vlp-ws/index.md so the note
reads a specific, actionable reference rather than TODO.
|
This PR will allow better tracking of the time when each workspace/modules are last tested. Since the turtlebot3 workspace and the Isaac ROS module seems to be found failing. @YuZhong-Chen @Assume-Zhan @JustinShih0918 @yuhsiang1117, would appreciate if you can help me fill in the TODOs. Let me know when did you last tested each of the workspaces/modules (and better if you know which commit) in the comments, thanks! |
This enables easier debugging if errors are observed when following the docs. For example, one can reset to that commit to see if the instructions are still working. If not, then the error might be due to some upstream dependency changes.
j3soon
force-pushed
the
docs/last-tested
branch
from
80a9923 to
507fc05
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@docs/docker-modules/rtabmap.md`:
- Around line 5-6: Replace the placeholder "TODO" in the line containing "Last
tested on TODO." with a concrete reproducible identifier: either a full git
commit hash (e.g., 40-char SHA) or an exact test date and time (YYYY-MM-DD or
YYYY-MM-DD HH:MM UTC); update the sentence to read like "Last tested on <commit
SHA>" or "Last tested on <YYYY-MM-DD>" so readers can reproduce the documented
state and verify which commit/date was used.
| > Last tested on TODO. | ||
|
|
There was a problem hiding this comment.
Replace “TODO” with a concrete commit or date.
Readers need a specific commit hash or exact test date to reproduce the documented state.
🤖 Prompt for AI Agents
In `@docs/docker-modules/rtabmap.md` around lines 5 - 6, Replace the placeholder
"TODO" in the line containing "Last tested on TODO." with a concrete
reproducible identifier: either a full git commit hash (e.g., 40-char SHA) or an
exact test date and time (YYYY-MM-DD or YYYY-MM-DD HH:MM UTC); update the
sentence to read like "Last tested on <commit SHA>" or "Last tested on
<YYYY-MM-DD>" so readers can reproduce the documented state and verify which
commit/date was used.
1 participant
This enables easier debugging if errors are observed when following the docs.
For example, one can reset to that commit to see if the instructions are still working. If not, then the error might be due to some upstream dependency changes.
Summary by CodeRabbit