Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix indentation in leaderboard README #449

Merged

Conversation

polm-stability
Copy link
Contributor

The code examples in the README use both triple backticks and indentation, which is not necessary and makes the code examples appear excessively indented. This is also annoying if you use the bash HISTCONTROL=ignorespace option, which causes commands prefaced with a space to not appear in history.

This PR removes the extra indentation.

Copy link
Collaborator

@HuanzhiMao HuanzhiMao left a comment

Choose a reason for hiding this comment

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

Thanks for contributing @polm-stability!

Copy link
Owner

@ShishirPatil ShishirPatil left a comment

Choose a reason for hiding this comment

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

Thank you @polm-stability

@ShishirPatil ShishirPatil merged commit fade5e4 into ShishirPatil:main May 30, 2024
@polm-stability polm-stability deleted the fix/readme-indentation branch May 30, 2024 09:48
devanshamin pushed a commit to devanshamin/gorilla that referenced this pull request Jul 9, 2024
The code examples in the README use both triple backticks and
indentation, which is not necessary and makes the code examples appear
excessively indented. This is also annoying if you use the bash
`HISTCONTROL=ignorespace` option, which causes commands prefaced with a
space to not appear in history.

This PR removes the extra indentation.

Co-authored-by: Paul O'Leary McCann <polm@dampfkraft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants