Automatisches Setzen des Upstream beim ersten Push, wenn kein Tracking-Branch existiert#24
Merged
timbornemann merged 1 commit intomasterfrom Apr 4, 2026
Conversation
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.
Motivation
PushFehler, weil kein Remote-Tracking-Branch existiert.Description
RunGitCommandOptionsumskipAutoSetUpstreamOnPushFailureinsrc/components/layout/state/appStateShared.tsals Schutz gegen rekursive Fallbacks.runGitCommand(src/components/layout/useAppState.ts) wurde eine Erkennung für typische no upstream Fehler hinzugefügt und die HilfsfunktiontryAutoSetUpstreamPushimplementiert, die bei einem fehlgeschlagenengit pushautomatisch mitgit push ... -u origin HEADnachsetzt.push-Befehle ausgelöst und respektiert vorhandene Push-Flags; bei Retry wird die Schutzoption gesetzt, damit keine Endlosschleife entsteht.Testing
npm run test:unitwurde ausgeführt und alle Unit-Tests liefen erfolgreich (113 passed).npm run build:electronwurde ausgeführt und der TypeScript-Build war erfolgreich.Codex Task