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

Enable and use GitHub Alert syntax for admonitions #275

Merged
merged 2 commits into from
Mar 5, 2024

Conversation

llucax
Copy link
Contributor

@llucax llucax commented Mar 4, 2024

This allows admonitions/callouts/alerts to be rendered properly both in GitHub and mkdocs. On the downside, GitHub syntax is less flexible than mkdocs, so we can't have the admonitions be rendered inline end any more.

Because of this we only use the GitHub syntax for the README, as it is more important that the README is rendered correctly in GitHub than having it look a bit nicer in mkdocs.

@llucax llucax requested a review from a team as a code owner March 4, 2024 11:01
@github-actions github-actions bot added part:docs Affects the documentation part:tooling Affects the development tooling (CI, deployment, dependency management, etc.) labels Mar 4, 2024
@llucax
Copy link
Contributor Author

llucax commented Mar 4, 2024

Before:

image

After:

image

This allows us to use [GitHub Alerts] in our markdown files, so
admonitions can render nicely on GitHub too.

[GitHub Alerts]: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#alerts

Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
This allows admonitions/callouts/alerts to be rendered properly both in
GitHub and `mkdocs`. On the downside, GitHub syntax is less flexible
than `mkdocs`, so we can't have the admonitions be rendered *inline end*
any more.

Because of this we only use the GitHub syntax for the README, as it is
more important that the README is rendered correctly in GitHub than
having it look a bit nicer in `mkdocs`.

Signed-off-by: Leandro Lucarella <luca-frequenz@llucax.com>
@shsms
Copy link
Contributor

shsms commented Mar 4, 2024

I wonder what requirement is missing.

@llucax llucax disabled auto-merge March 5, 2024 10:11
@llucax llucax added this pull request to the merge queue Mar 5, 2024
@llucax
Copy link
Contributor Author

llucax commented Mar 5, 2024

I guess it got borked when I switched the merge queue from a "branch protection" to a "ruleset" #GitHub 🦄

Merged via the queue into frequenz-floss:v1.x.x with commit 27f70c2 Mar 5, 2024
14 checks passed
@llucax llucax deleted the github-callouts branch March 5, 2024 10:19
@llucax llucax modified the milestones: v1.0.0, v1.0.0-rc.1 Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
part:docs Affects the documentation part:tooling Affects the development tooling (CI, deployment, dependency management, etc.)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants