Bug 643397: Miapp uses a stale RepoBranchName - #9701
Closed
AleksanderGladkov wants to merge 1 commit into
Closed
Conversation
github-actions
Bot
added
Build: scripts & configs
ventselartur
approved these changes
Jul 23, 2026
mazhelez
approved these changes
Jul 23, 2026
AleksanderGladkov
enabled auto-merge
July 23, 2026 17:20
AleksanderGladkov
disabled auto-merge
July 27, 2026 08:54
Contributor
Author
|
Partially solved in The solution in the PR 9713 will work in master, but will not work in releases/28.x |
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
3 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.
ISSUE:
Initialize NAV enlistment, cd App/BCApps, run Invoke-Miapp.
It fails with the error: Exception: fatal: HEAD does not point to a branch
Miapp fails in BCApps when
RepoBranchNamecontains a stale value from another repository, such asmasterfrom NAV.CAUSE:
Miapp trusts the environment value without checking whether the branch exists on the current repository's
origin.SOLUTION:
Preserve valid explicit base branches. When the configured branch does not exist on
origin, show a warning and fall back to the current repository'sorigin/HEAD.TESTS:
Validated valid, unset, and stale base-branch values. Verified that
Invoke-Miappautomatically usesmainwhen the inherited value ismaster.Fixes AB#643397