Github desktop wont push to fork4/15/2024 ![]() I suspect there was a problem with the update that was applied from 2.9.7 to 2.9.8. I tried chanigng the property to 2.9.8, but this did not fix the issue.Īn un-install and re-install of GitHubDesktop resolved the issue. The logs show that version 2.9.8 had been installed. If you try to connect with your GitHub username, it will fail: ssh -T > Permission denied (publickey). The shortcut "Start in" property on the shortcut was pointing at 2.9.7. All connections, including those for remote URLs, must be made as the 'git' user. LogsĪttach your logs by opening the Help menu and selecting Show Logs., if applicable. code using Github Desktop on macOS Learn how to setup Github, clone your code locally, as well as comit and push changes in a smart and clean manner. There is no hourglass or indication that anything is trying to start. Also because i have deleted Github desktop folder in roaming and Local before re-installing I don't have the old logs. I expect githubdesktop to open Actual behavior I can see github desktop running in task manager so i guess it doesn't create crash log. Click on Shortcuts or double click on exe.OS - Windows 11 Steps to reproduce the behavior If you're new to Git and GitHub, you may find it easier to use. GitHub Desktop is useful for beginning and advanced users. I also couldn't find anything in the GitHubDesktop logs Version & OS GitHub Desktop is a free, open source application that helps you to work with files hosted on GitHub or other Git hosting services. There is nothing showing in windows event logs. Push will instead show a dialog to create a new repository instead of pushing to existing remote origin.GitHubDesktop will not launch from toolbar shortcut, menu shortcut or directly when double clicking on. Push should work as expected on this repo. Observe Desktop fails to push and shows a dialog for creating a new repo instead.Observe ink-rs repo is placed in "Other" section of repository list, not section.Since I use two-factor auth, it's easier to use Desktop than hunt for a personal access token for command line, so I usually just use Desktop for other repositories. When they try to push their most recent changes the following error appears On branch main Your branch is up to date with 'origin/main'. We've run into a problem with one of our contributors using GitHub desktop. If I try to push using command line, it works. 1 This question does not show any research effort it is unclear or not useful Save this question. Using the same name fails with an errors saying it already exists. ![]() You can clone your fork with the command line, GitHub CLI, or GitHub Desktop. To be able to work on the project, you will need to clone it to your computer. When you do this, your changes become part of the main project. You've successfully forked the Spoon-Knife repository, but so far, it only exists on GitHub. Whenever I have local changes to push, if I try to use Desktop it brings up a dialog prompt as if I'm pushing a brand new repository to GitHub, asking for name, etc. In Git, you create branches by starting with either the head/trunk or an existing branch. ![]() This wouldn't be a problem, but somehow Desktop doesn't recognize the remote when I try to push. Yet when I clone the repo using Desktop, it places in the "Other" section of the repositories list, not the section. My repository is hosted at and is public. Other repositories work fine, just this one single repo has issues. GitHub Desktop doesn't recognize one of my repositories as being from GitHub and fails to push.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |