Handle git push when there is no remote - #54522
Merged
ChristopherBiscardi merged 1 commit intoApr 22, 2026
Merged
Conversation
cla-bot
Bot
added
the
cla-signed
zed-community-bot
Bot
added
the
staff
cole-miller
self-requested a review
April 22, 2026 18:13
cole-miller
approved these changes
Apr 22, 2026
kathbigra
pushed a commit
to kathbigra/zed
that referenced
this pull request
May 10, 2026
Previously hitting `Publish` in the git panel would silently fail with no error message if the git repo was new or didn't have a remote. Now, when hitting `Publish` or attempting to push when there is no remote using keyboard shortcuts, or using `Push To` or force push options, an error message will be displayed. <img width="1135" height="522" alt="Screenshot 2026-04-22 at 10 02 26 AM" src="https://github.com/user-attachments/assets/93c5e7ee-371e-4c2c-961b-42501cbd7119" /> <img width="1135" height="522" alt="Screenshot 2026-04-22 at 10 02 36 AM" src="https://github.com/user-attachments/assets/a923e5f2-4099-45b5-8fe2-eb78f4fc9f10" /> Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Release Notes: - Fixed handling of `git push` when there is no remote available to push to
jonx
pushed a commit
to jonx/zed-aros
that referenced
this pull request
Jul 17, 2026
Previously hitting `Publish` in the git panel would silently fail with no error message if the git repo was new or didn't have a remote. Now, when hitting `Publish` or attempting to push when there is no remote using keyboard shortcuts, or using `Push To` or force push options, an error message will be displayed. <img width="1135" height="522" alt="Screenshot 2026-04-22 at 10 02 26 AM" src="https://github.com/user-attachments/assets/93c5e7ee-371e-4c2c-961b-42501cbd7119" /> <img width="1135" height="522" alt="Screenshot 2026-04-22 at 10 02 36 AM" src="https://github.com/user-attachments/assets/a923e5f2-4099-45b5-8fe2-eb78f4fc9f10" /> Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Release Notes: - Fixed handling of `git push` when there is no remote available to push to
jolutz
pushed a commit
to jolutz/zed
that referenced
this pull request
Aug 8, 2026
Previously hitting `Publish` in the git panel would silently fail with no error message if the git repo was new or didn't have a remote. Now, when hitting `Publish` or attempting to push when there is no remote using keyboard shortcuts, or using `Push To` or force push options, an error message will be displayed. <img width="1135" height="522" alt="Screenshot 2026-04-22 at 10 02 26 AM" src="https://github.com/user-attachments/assets/93c5e7ee-371e-4c2c-961b-42501cbd7119" /> <img width="1135" height="522" alt="Screenshot 2026-04-22 at 10 02 36 AM" src="https://github.com/user-attachments/assets/a923e5f2-4099-45b5-8fe2-eb78f4fc9f10" /> Self-Review Checklist: - [x] I've reviewed my own diff for quality, security, and reliability - [x] Unsafe blocks (if any) have justifying comments - [x] The content is consistent with the [UI/UX checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) - [x] Tests cover the new/changed behavior - [x] Performance impact has been considered and is acceptable Release Notes: - Fixed handling of `git push` when there is no remote available to push to
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
2 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.
Previously hitting
Publishin the git panel would silently fail with no error message if the git repo was new or didn't have a remote.Now, when hitting
Publishor attempting to push when there is no remote using keyboard shortcuts, or usingPush Toor force push options, an error message will be displayed.Self-Review Checklist:
Release Notes:
git pushwhen there is no remote available to push to