Skip to content

Conversation

@Flova
Copy link
Member

@Flova Flova commented Oct 31, 2024

Summary

Fix ~ folder issue, links and ssh setup

@Flova Flova requested review from jaagut and texhnolyze October 31, 2024 21:19
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 31, 2024

Walkthrough

The pull request introduces modifications to two documentation files related to setup instructions for CL simulation testing and the installation of ROS2 Iron Irwini on Ubuntu 22.04. The changes include enhanced clarity in the setup steps, detailed prerequisites, and improved formatting for links and commands. Sections have been added or expanded to provide users with comprehensive guidance on SSH key setup, directory creation, compilation, and debugging tools, as well as a streamlined installation process for ROS2.

Changes

File Path Change Summary
bitbots_misc/bitbots_docs/docs/manual/tutorials/cl_simulation_testing_setup.rst Updated SSH key setup instructions, simplified directory commands using $HOME, clarified simulation command context, and expanded debugging instructions.
bitbots_misc/bitbots_docs/docs/manual/tutorials/install_software_ros2.rst Enhanced tutorial for installing ROS2 Iron Irwini, maintaining a TLDR section, detailing prerequisites, expanding installation steps, and improving hyperlink formatting.

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 33214de and aef1091.

📒 Files selected for processing (1)
  • bitbots_misc/bitbots_docs/docs/manual/tutorials/install_software_ros2.rst (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • bitbots_misc/bitbots_docs/docs/manual/tutorials/install_software_ros2.rst

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Outside diff range and nitpick comments (2)
bitbots_misc/bitbots_docs/docs/manual/tutorials/install_software_ros2.rst (2)

73-73: LGTM! Consider these minor improvements for clarity.

The SSH key setup instructions are clear and well-structured. Consider these enhancements:

  1. Use a relative link for the bit-bots documentation instead of an absolute URL to prevent broken links if the domain changes
  2. Add a note about supported SSH key types (Ed25519 is recommended)

Apply this change to use a relative link:

-see `here <http://doku.bit-bots.de/private/manual/dienste_accounts.html>`_
+see :doc:`here <../dienste_accounts>`

73-73: Enhance documentation of environment variables.

The "Final touches" section could benefit from additional documentation:

  1. Add comments explaining the purpose of ROS_DOMAIN_ID=24 and when users might need to change it
  2. Document the significance of COLCON_LOG_LEVEL=30
  3. Consider adding a troubleshooting section for common setup issues
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between b226971 and 988d72b.

📒 Files selected for processing (2)
  • bitbots_misc/bitbots_docs/docs/manual/tutorials/cl_simulation_testing_setup.rst (1 hunks)
  • bitbots_misc/bitbots_docs/docs/manual/tutorials/install_software_ros2.rst (1 hunks)
🔇 Additional comments (1)
bitbots_misc/bitbots_docs/docs/manual/tutorials/cl_simulation_testing_setup.rst (1)

17-19: LGTM: Clear and comprehensive SSH setup instructions.

The added SSH key setup instructions are well-structured and provide excellent guidance, including:

  • Link to official GitHub documentation for new users
  • Clear specification of using the .pub file
  • Proper RST formatting for external links

**3. Download our software**

- Create a GitHub account, if not already done (see `here <http://doku.bit-bots.de/private/manual/dienste_accounts.html>` for further information)
- Create a GitHub account, if not already done (see `here <http://doku.bit-bots.de/private/manual/dienste_accounts.html>`_ for further information)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Add security best practices for SSH key setup.

Consider adding these security-related notes:

  1. Set correct permissions for SSH keys: chmod 600 ~/.ssh/id_ed25519
  2. Never share or expose your private key
  3. Use a strong passphrase for your SSH key

…testing_setup.rst

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Copy link
Member

@jaagut jaagut left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As code rabbit suggested, we should consider using more relative links.

Also, after the install ros step with concatenating the bashrc: one has to either

  • source bashrc manually,
  • close the session, reopen and the next step still assumes, we are in the ws/src/bitbots_main directory which we are not
  • or call bash again

I think, sourcing is the cleanest option. We should add this to the install ros doc

@Flova
Copy link
Member Author

Flova commented Nov 2, 2024

As code rabbit suggested, we should consider using more relative links.

I agree, but I think this is out of scope for this PR.

Auto source new .bashrc
@Flova Flova requested a review from jaagut November 2, 2024 14:02
@Flova Flova merged commit e541749 into main Nov 2, 2024
3 checks passed
@Flova Flova deleted the fix/setup_guide branch November 2, 2024 17:12
@Flova Flova added the docs label Nov 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: ✅ Done

Development

Successfully merging this pull request may close these issues.

3 participants