Feature/kiri explicit commits#946
Merged
Merged
Conversation
Member
|
Hi @hamletg ! |
Add commits and labels options to the KiRi output so users can compare specific git revisions (tags, hashes, branches) instead of only the last N commits from a revision range. When commits is not empty it takes precedence over max_commits and revision. Optional labels replace commit subjects in the KiRI UI. Co-authored-by: Cursor <cursoragent@cursor.com>
When include_dirty is false, uncommitted schematic/PCB changes are not prepended to the KiRI commit list. Co-authored-by: Cursor <cursoragent@cursor.com>
hamletg
force-pushed
the
feature/kiri-explicit-commits
branch
from
July 13, 2026 13:51
5db69bd to
b7a4ebd
Compare
Author
|
I rebased it on dev. I was not entirely sure what to do with the change log, but I did what I could. |
Member
|
You have to use the |
Author
|
The problem was that I made the PR against master, not dev. After changing the target of the PR to dev, only 2 commits are seen in the PR, as it was in my branch. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR extends the KiRi output with explicit revision lists for release comparisons, and adds control over whether uncommitted local changes appear in the commit list.
Motivation
KiRi’s default mode uses revision + max_commits to collect commits from git log. That works for “recent changes” views, but not for release-to-release comparisons where you want exactly two (or more) tagged board versions, in a specific order, with readable labels.
We also need a way to omit local from CI-generated KiRi pages when KiBot temporarily dirties the working tree during the run.
Output example
One PCB I started working on