You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e611e22
Browse filesBrowse the repository at this point in the historyBrowse files
fix(builder): append the mirror mappings only after a plain inherited count
Moving inherited git config after the mirror mappings could not win
precedence anyway (git breaks insteadOf ties by the order the
destination base was registered, so a system or global rewrite still
wins) and added edge cases of its own. The mappings are appended after
the inherited entries again, without reading or moving them. They are
used only when GIT_CONFIG_COUNT is unset, empty, or a plain count of at
most four digits once one leading "+" and leading zeros are dropped;
otherwise the git configuration is left alone, the build log says the
sources are fetched without the mirror, and the build runs as it does
today.
An image whose own git configuration (system, global or environment)
already rewrites a declared repository's URL keeps its rewrite: git
prefers it, and the build fetches that source as it does without a
mirror.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
require.Equal(t, "inherited GIT_CONFIG_COUNT is not a plain count; git sources are fetched without the mirror\ncount=["+count+"] keys=1 prompt=[]\n", out)
374
+
})
375
+
}
376
+
// The limitation, as it is today without a mirror: an image whose own git
377
+
// configuration rewrites a declared URL keeps its rewrite, which git
378
+
// prefers, so the source is fetched where the image says, not broken.
379
+
t.Run("inherited rewrite of a declared URL", func(t*testing.T) {
0 commit comments