Skip to content

docs: Fix code blocks code generation#4693

Merged
simonswine merged 1 commit intomainfrom
20251216_fix-api-docs
Dec 23, 2025
Merged

docs: Fix code blocks code generation#4693
simonswine merged 1 commit intomainfrom
20251216_fix-api-docs

Conversation

@simonswine
Copy link
Contributor

@simonswine simonswine commented Dec 16, 2025

Before:

image

After:

image

@simonswine simonswine added the backport release/v1.16 This label will backport a merged PR to the release/v1.16 branch label Dec 16, 2025
@simonswine simonswine marked this pull request as ready for review December 16, 2025 15:30
@simonswine simonswine requested review from a team as code owners December 16, 2025 15:30
@simonswine simonswine merged commit 8813f79 into main Dec 23, 2025
21 checks passed
@simonswine simonswine deleted the 20251216_fix-api-docs branch December 23, 2025 09:14
@pyroscope-development-app
Copy link
Contributor

Hello @simonswine!
Backport pull requests need to be either:

  • Pull requests which address bugs,
  • Urgent fixes which need product approval, in order to get merged,
  • Docs changes.

Please, if the current pull request addresses a bug fix, label it with the type/bug label.
If it already has the product approval, please add the product-approved label. For docs changes, please add the type/docs label.
If the pull request modifies CI behaviour, please add the type/ci label.
If none of the above applies, please consider removing the backport label and target the next major/minor release.
Thanks!

@simonswine simonswine added the type/docs Improvements for doc docs. Used by Docs team for project management label Dec 23, 2025
@pyroscope-development-app
Copy link
Contributor

Hello @simonswine!
Backport pull requests need to be either:

  • Pull requests which address bugs,
  • Urgent fixes which need product approval, in order to get merged,
  • Docs changes.

Please, if the current pull request addresses a bug fix, label it with the type/bug label.
If it already has the product approval, please add the product-approved label. For docs changes, please add the type/docs label.
If the pull request modifies CI behaviour, please add the type/ci label.
If none of the above applies, please consider removing the backport label and target the next major/minor release.
Thanks!

simonswine added a commit that referenced this pull request Dec 23, 2025
* docs: Fix code blocks code generation (#4693)

* docs: update release notes for v1.17, v1.16.x & v1.15.x (#4710)

---------

Co-authored-by: Marc Sanmiquel <marcsanmiquel@gmail.com>
simonswine added a commit that referenced this pull request Dec 23, 2025
* docs: Fix code blocks code generation (#4693)

* docs: update release notes for v1.16.x & v1.15.x (#4710)

---------

Co-authored-by: Marc Sanmiquel <marcsanmiquel@gmail.com>
simonswine added a commit that referenced this pull request Dec 23, 2025
* docs: Fix code blocks code generation (#4693)

* docs: update release notes for v1.15.x (#4710)

---------

Co-authored-by: Marc Sanmiquel <marcsanmiquel@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport release/v1.16 This label will backport a merged PR to the release/v1.16 branch missing-labels type/docs Improvements for doc docs. Used by Docs team for project management

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants