Conversation
Opening a project that has no repository still refreshes the panel, so `git remote -v` runs and reports there is no repository. That landed as a modal error over the editor — for the project the user had just chosen themselves, and on every switch to a non-git folder. Treat that one failure as the ordinary condition it is: clear the remote picker and keep the reason in the log. Every other remotes failure still raises the dialog.
The history table listed every commit alike, so nothing said which of them the remote already has, or whether the branch had ever been pushed at all. Draw a waterline where the remote's branch points. Commits above it carry the same orange left edge the gutter puts on a modified line, so "edge means not saved upstream yet" reads the same in the editor and here. The marker takes its colour from the state it describes: blue while there is nothing to push, orange once commits are waiting, so the run of orange above closes on an orange line and reads as one mark. A branch with no counterpart on the remote gets a "not pushed" banner instead, closed off at the initial commit once the whole history is on screen. Where the remote points comes from one `for-each-ref` reading the branch and the remote ref together — the branch row carries the upstream's name, the remote row the hash. A branch tracking some other ref needs a second call; nothing else does, and paging costs none, since the answer latches once the waterline is placed. File history is left alone: it lists only the commits touching one file, so the remote's head is usually not among them and every row would be wrongly called local.
|
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
1 participant
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.
No description provided.