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.

Sign up for GitHub

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

Jump to bottom

Bot configuration examples use JSON instead of YAML #2066

Closed
ghost opened this issue Aug 24, 2021 · 1 comment
Closed

Bot configuration examples use JSON instead of YAML #2066

ghost opened this issue Aug 24, 2021 · 1 comment
Labels
bug Indicates an unexpected problem or unintended behavior documentation Indicates a need for improvements or additions to documentation good first issue Indicates a good issue for first-time contributors help wanted Indicates that a maintainer wants help on an issue or pull request

Comments

@ghost
Copy link

ghost commented Aug 24, 2021

There are numerous configuration examples in docs/user/bots.rst (and in some other documentation files) which are still in json format - they should be converted to yaml (this would then also fix the Could not lex literal_block as "json". warnings)
@ghost ghost added documentation Indicates a need for improvements or additions to documentation good first issue Indicates a good issue for first-time contributors bug Indicates an unexpected problem or unintended behavior labels Aug 24, 2021
@sebix sebix added the help wanted Indicates that a maintainer wants help on an issue or pull request label Feb 3, 2022
@sebix sebix changed the title Convert config examples in bots.rst to yaml Bot configuration examples use JSON instead of YAML Aug 8, 2022
@gethvi
Copy link
Contributor

gethvi commented Jan 8, 2024

Done.

@gethvi gethvi closed this as completed Jan 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Indicates an unexpected problem or unintended behavior documentation Indicates a need for improvements or additions to documentation good first issue Indicates a good issue for first-time contributors help wanted Indicates that a maintainer wants help on an issue or pull request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sebix @gethvi