How to turn a JUnit XML report into an Obsidian note
As of October 2026, the Obsidian core plugin list describes no JUnit report converter.
How to draft release notes from commit subjects in Obsidian
As of October 2026, the Obsidian core plugin list describes no commit subject grouper. You can group subjects in a Markdown note yourself or use Conventional Commit Draft. Check commit bodies separately for breaking change details.
Background
The Conventional Commits specification gives feature and fix types distinct meanings. It permits breaking changes in a footer or subject marker. A subject list can miss information that exists only in a body.
3 ways to do it
Group the subjects by hand
Create a Markdown note with headings for features and fixes. Place subjects under the matching headings, then read the original changes before you describe compatibility effects.
- limits
- You must check types and group the subjects yourself. Keep body details beside the draft if they affect the release.
Generate notes in GitHub
For a GitHub repository, the release form can generate notes from merged pull requests. A configuration file can group pull requests by labels and exclude selected labels or authors.
- limits
- This method uses repository pull requests. It does not group an arbitrary selection from your Obsidian note.
Conventional Commit Draft from this site
Select subjects in an editable note and run Preview release draft from selection. The preview groups recognized types and keeps uncertain lines under Review. Save a separate note after you check the text.
- limits
- Input stops at 2,000 nonblank lines. Saved headings and named templates need Pro, and commit bodies do not supply breaking labels.
Open larger MIT · no telemetry · core features free
Create a local release draft
Open a Markdown note in an editable view and select one commit subject per line.
Run Preview release draft from selection from the command palette.
Check the groups, scopes, BREAKING labels and Review lines.
Set a release title and project name, then select Save new draft.
Open the new note from the file explorer.
Common questions
Does a subject list prove which version to release?
No. The specification relates types and breaking changes to version changes. Check the changes and body details before choosing a version.
How can I keep a project type visible?
The free draft places a parsed project type under Other with its type name. Pro lets you give that type a saved heading. Lines that do not parse stay under Review.
Sources
- Conventional Commits specificationconventionalcommits.org
- Obsidian core pluginshelp.obsidian.md
- Obsidian basic formatting syntaxhelp.obsidian.md
- GitHub generated release notesdocs.github.com
- Conventional Commit Draft sourcegithub.com
That's every step, start to finish.
You're officially a regular.
Obsidian rewards people who share. NoteMods is just me and a lot of coffee. If this guide saved you a fight with the syntax, buy me a cup.
That's visit . Regulars are the reason I keep NoteMods running. If it's part of your routine now, a coffee says thanks better than anything.
The plugin in this guide
Conventional Commit Draft
Turn selected commit subjects into a release draft that you can review before saving.