Skip to content

docs: use correct jinja content-type #6296

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
Merged
merged 1 commit into from
Jul 8, 2025
Merged

docs: use correct jinja content-type #6296

merged 1 commit into from
Jul 8, 2025

Conversation

TheRealFalcon
Copy link
Member

Proposed Commit Message

docs: use correct jinja content-type

Fixes GH-6027

Additional Context

Test Steps

Merge type

  • Squash merge using "Proposed Commit Message"
  • Rebase and merge unique commits. Requires commit messages per-commit each referencing the pull request number (#<PR_NUM>)

@github-actions github-actions bot added the documentation This Pull Request changes documentation label Jul 8, 2025
blackboxsw
blackboxsw approved these changes Jul 8, 2025
View reviewed changes
Copy link
Collaborator

@blackboxsw blackboxsw left a comment

Choose a reason for hiding this comment

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

Ship it!

@blackboxsw blackboxsw merged commit ff1d9f0 into canonical:main Jul 8, 2025
22 checks passed
@TheRealFalcon TheRealFalcon deleted the jinja-doc branch July 8, 2025 16:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@blackboxsw blackboxsw blackboxsw approved these changes

Assignees
No one assigned
Labels
documentation This Pull Request changes documentation
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@TheRealFalcon @blackboxsw