You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the repository, there is an inconsistency in the formatting of code snippets between sections. Specifically:
In the "Requesting a VPS" section:
Code snippets are provided separately for Ubuntu and RedHat systems.
In the "Configure SSH Tunneling" section:
Code snippets are written in Bash but use inconsistent formatting:
Some lines begin with the $ sign to indicate a shell prompt.
Other lines omit the $ sign entirely.
This inconsistency can cause confusion for readers, as it mixes conventions and does not clearly distinguish between command input and expected output.
Proposed Solution
To address this, we could establish a code snippet syntax guideline for the repository.
Command Prompt Indicator:
Use the $ sign consistently in all code snippets to indicate a shell prompt or not use it at all for easy of copying.
Cross-Platform Snippets:
Use consistent formatting for snippets targeting different systems (e.g., Ubuntu and RedHat). If a previous step has Ubuntu prompt, we should assume that the user will keep using Ubuntu in the next step.
I propose the following action items
Decide on the formatting rules for command snippets.
Update the code snippets in the "Configure SSH Tunneling" section to match the agreed guidelines.
Add a contributing guide or style guide outlining these rules for future contributions.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In the repository, there is an inconsistency in the formatting of code snippets between sections. Specifically:
In the "Requesting a VPS" section:
In the "Configure SSH Tunneling" section:
$
sign to indicate a shell prompt.$
sign entirely.This inconsistency can cause confusion for readers, as it mixes conventions and does not clearly distinguish between command input and expected output.
Proposed Solution
To address this, we could establish a code snippet syntax guideline for the repository.
Command Prompt Indicator:
$
sign consistently in all code snippets to indicate a shell prompt or not use it at all for easy of copying.Cross-Platform Snippets:
I propose the following action items
Beta Was this translation helpful? Give feedback.
All reactions