Repository navigation
Search the release branch first for a commit to tag - #607
Open
CiaranOMara wants to merge 1 commit into
Open
CiaranOMara wants to merge 1 commit into
CiaranOMara wants to merge 1 commit into
Conversation
CiaranOMara
force-pushed
the
prefer-release-branch
branch
from
October 27, 2026 06:05
934ce6c to
00fa6f9
Compare
The README says that the branch set by the `branch` input is the first one searched for a commit to tag, but the tree→commit cache read `git log --all` alone, keeping the most recent commit for each tree. Where several commits share a registered tree, such as a release's merge commit on the release branch and a later merge of it into a development branch under gitflow, TagBot tagged the latter, which the registry didn't register and which isn't on the release branch. With `branch` set, the cache now reads that branch's history first, then the full history, so the commit on the release branch wins. The subdirectory cache, derived from the full cache, follows. Without `branch`, the cache is built as before.
CiaranOMara
force-pushed
the
prefer-release-branch
branch
from
October 27, 2026 06:07
00fa6f9 to
db27c47
Compare
This branch has not been deployed
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
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.
The README says that the branch set by the
branchinput is the first one searched for a commit to tag, but the tree→commit cache readgit log --allalone, keeping the most recent commit for each tree. Where several commits share a registered tree, such as a release's merge commit on the release branch and a later merge of it into a development branch under gitflow, TagBot tagged the latter, which the registry didn't register and which isn't on the release branch.With
branchset, the cache now reads that branch's history first, then the full history, so the commit on the release branch wins. The subdirectory cache, derived from the full cache, follows. Withoutbranch, the cache is built as before.